Ballot Details: Defer VIRTIO-177: "what follows" 4 instances; "below" 17 instances; "follows" 47 instances (CLOSED)

Ballot Question Should the TC defer issue VIRTIO-177 after specification version(s) "virtio-v1.1-cs01"?
Ballot Description Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.

I move that:
The TC agrees to defer resolving the following specification issue:
VIRTIO-177: "what follows" 4 instances; "below" 17 instances; "follows" 47 instances
--------------------------------------
In terms of accessibility, "what follows," "below," and "follows" all inhibit the use of VIRTIO by users assisted by reading software.

Take 2.2 Feature Bits as an example:

"Feature bits are allocated as follows:

0 to 23 Feature bits for the specific device type

24 to 37 Feature bits reserved for extensions to the queue and feature negotiation mechanisms

38 and above Feature bits reserved for future extensions."

A sighted reader is clued in that 3 entries follow, but reading software does not offer, in this form, the same clue.

Compare:

"Feature bits are allocated in three ways:

1. 0 to 23 Feature bits for the specific device type

2. 24 to 37 Feature bits reserved for extensions to the queue and feature negotiation mechanisms

3. 38 and above Feature bits reserved for future extensions."

Same text but now both sighted as well as assisted readers know there are 3 ways to allocate feature bits and each of those ways is numbered and recited to the reader.

 

 

 
--------------------------------------

The TC agrees that the issue will not be resolved for the revision
"virtio-v1.1-cs01" of the specification.

Justification:
--------------------------------------
Accessibility is a very important topic to address.

However coming up with a better scheme won't be easy:
we'll need different changes in different places in code.

In the quoted example what follows is just a list in no particular order.
So saying "there are three ways" and numbering them would cause
confusion.

Lots of accesibility sites warn against nesting of unordered lists
but avoiding them completely seems overbroad. See e.g.
http://accessibility.psu.edu/listshtml/

--------------------------------------

--------------------------------------

Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.

--------------------------------------
Ballot Options
VOTING CLOSED: Friday, 15 March 2019 @ 1:00 am EDT
Yes 5 100
No 0 0
Abstain 0
Open Date Friday, 8 March 2019 @ 1:00 am EST
Close Date Friday, 15 March 2019 @ 1:00 am EDT
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 5
Eligible members who have voted 5 of 6 83.333%
Eligible members who have not voted 1 of 6 16.667%

Voting Summary by Option

Options with highest number of votes are bold
Option # Votes % of Total
Yes 5 100%
No 0 0%
Abstain 0

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Carabas, Mihai Oracle Yes 2019-03-08 08:04:00
* Hajnoczi, Stefan Red Hat Yes 2019-03-08 10:13:00
* Huck, Cornelia Red Hat Yes 2019-03-08 10:43:00
* Pasic, Halil IBM Yes 2019-03-12 12:23:00
* Tsirkin, Michael S. Red Hat Yes 2019-03-08 06:26:00
* Kiszka, Jan Siemens AG --