w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody.
This questionnaire was open from 2017-10-12 to 2017-11-14.
3 answers have been received.
Jump to results for question:
Do we want to deprioritize Simplification and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Simplification: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | I don't think we WANT to but I think we HAVE to unless we can figure out how to actually do it. Otherwise it is a great thought but a bad requirement. 1) This should say that it should be programmatically determinable which category it goes in -- so that AT or browsers could present different levels of information to the user - not just have them all there with markings next to them making it more complicated to view/read. 2) the definition of the levels is problemmatic. We need to figure out how to do these better. My experience is that it is so easy to mess with these types of definitions. For example -- I have a shopping site. only 18-20 % of the people who come to the site actually buy something. So all of the checkout parts are only medium to low priority -- and would disappear if people asked to show only the important things. Also - I did research and my ads are intrusive enough that my data show that 70% of the people see/read them. So they are most important. and for my site to stay up - I certainly think they are important. so now we have a shopping site with the add shown but not the checkout parts? or rather - whatever I want to show showing as important. PERHAPS - we can look to definitions that look like "all the parts absolutely required for use of the site -- but when we looked at this in WCAG 2.0 -- we found that not showing people discounts and sales was discriminatory -- they needed to see the sales as well. And most of the features - someone thought were really important for some users with disabilities. We ended up not being able to define "what was important" in a way that someone else on the team could not poke a hole in. Maybe if we can think of categories of information instead of saying importance. Body Navigation Checkout Advertising etc -- thought people HATE to tag their advertisements because that is how they make the money to keep their sites up. so LOVE the idea but don't see how to do it |
Charles LaPierre | no |
Do you know of any intended implementations of Simplification? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 2 |
no | 1 |
Responder | Simplification Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | Easyreader - using these semantics is explicit in the proposal |
Gregg Vanderheiden | yes | The best I have seen is where there is a simple version at top or bottom. Acts as kind of an abstract. |
Charles LaPierre | no |
Do we want to deprioritize Adding Context and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Adding Context: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | I think this one is a winner -- But I think we should change any requirement to say that the requirement can be met if you EITHER use the "name-from-list-of-coga-names" as the name on the item itself OR you add the coga-xxxx=coganame attribute to the item. EITHER one can be used. That way we don't create a lot of extra work for people useing standard names. the only problem with this is that you need to define your list of common names in all the different languages of the world. But you need to do that anyway. And you can't use translators. For example HOME button is a translation of START in some languages -- not a translation of the word HOME. and SUBMIT might translate into "surrender" or "capitulate" which is a pretty strange button on a form. by the way -- who is working on all of the translations of all of the words on all of our lists into all of the different languages of the Web? |
Charles LaPierre | no |
Do you know of any intended implementations of Adding Context? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Adding Context: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | easyreader and the athena plugin |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do we want to deprioritize Concept Codes and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Concept Codes: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | yes | only because we have nothing there. And we have not figured out how to handle the problems with the above items. But I think it is ok to have a comment about what this concept is. However I would not include it if we don't have some good examples. |
Charles LaPierre | no |
Do you know of any intended implementations of Concept Code? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Concept Codes: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | Easyreader - using these semantics is explicit in the proposal |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do we want to deprioritize Potential parts of a page and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Potential parts of a page: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | Ah this looks like what I described above about tagging different parts of the page by function. |
Charles LaPierre | no |
Do you know of any intended implementations of Potential parts of a page? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 2 |
no | 1 |
Responder | Potential parts of a page: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | AThena plug in, maybe easyreader |
Gregg Vanderheiden | yes | We would do this - especially for our template pages on GPII.net and http://raisingthefloor.org |
Charles LaPierre | no |
Do we want to deprioritize Number free and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Number free: Prioritization | |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | if this is going to be required at any time (e.g. Level a or level aa) then I would deprioritize I think it is a great idea where it can work but I see absolutely no way to apply this in most cases. My bank account a budget any spreadsheet any shopping site (expensive is very relative) any comparison site (what does 8 watts convert into?) etc. |
Charles LaPierre | no |
Do you know of any intended implementations of Number free? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Number free: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | Easyreader - using these semantics is explicit in the proposal |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do we want to deprioritize Non-literal text and images and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Non-literal text and images: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | This is a pretty clear one. I think it has some trouble with determining edge cases but if we use "commonly recognized" There is a form of it in WCAG 2 3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA) this could be a mechanism for doing this. |
Charles LaPierre | no |
Do you know of any intended implementations of Non-literal text and images? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 2 |
no | 1 |
Responder | Non-literal text and images: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | Easyreader - using these semantics is explicit in the proposal |
Gregg Vanderheiden | yes | See Understanding WCAG 2.0 |
Charles LaPierre | no |
Do we want to deprioritize Explain and feedback and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Explain and feedback: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do you know of any intended implementations of Explain and feedback? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Explain and feedback: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | maybe easyreader and maybe athena plugin |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do we want to deprioritize More Help and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | More Help: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | Not sure I understand this one. I thought it was straightforward -but there is not text in the documents so that makes me wonder but i think that it could be doable SIDE COMMENT - I notice that we start each one of these with REQUIREMENT but what follows isnt a requirement but a NEED. Should we change 'requirement' to 'need' on the front of each one. (excuse CAPS but there is no bold formatting allowed in this field to add emphasis .) |
Charles LaPierre | no |
Do you know of any intended implementations of More Help? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 1 |
(1 response didn't contain an answer to this question)
Responder | More Help: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | implicit in easyreader I also know of somone in IBM who was interesting in devloping a plugin around it. I am not sure what is happening with that |
Gregg Vanderheiden | ||
Charles LaPierre | no |
Do we want to deprioritize Potential Features and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 2 |
(1 response didn't contain an answer to this question)
Responder | Potential Features: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | this should be merged |
Gregg Vanderheiden | Have no idea what this one means. there is no explanation | |
Charles LaPierre | no |
Do you know of any intended implementations of Potential Features? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Potential Features: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | not sure |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do we want to deprioritize Language type support and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Language type support: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | This is a good one. but I would drop the use of legal documents as an example. It may be (and probably is) illegal to have someone rely on a summary and then sign a document where that language is not the language that the user is held to. so great idea - but not for legal documents (which have to be written to be more understandable in the first place since they are binding as they are written - not in simpler language). Or at least we don't want to have that debate on this item which is a good item. |
Charles LaPierre | no |
Do you know of any intended implementations of Language type support? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 2 |
no | 1 |
Responder | Language type support: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | explicit in easyreader |
Gregg Vanderheiden | yes | lflegal.org but not using aria |
Charles LaPierre | no |
Do we want to deprioritize Logs and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Logs: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | interesting idea but needs better name than LOGS. Keeping logs has all sorts of privacy and tracking implications. Also we need to cover all of those before this is ready to view Some of this looks like progress tracking rather than logs (here are the steps in the process and here is where you are) which is great but I think of logs as things that are kept. Maybe "Progress and Place markers" |
Charles LaPierre | yes | I think this may be in jeopardy of being more complicated and could take extra time to get right if we need to have any type of validation of parts needed to be correct. |
Do you know of any intended implementations of Logs? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Logs: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | I also know of somone in IBM who was devloping a plugin around it. I am not sure what is happening with that |
Gregg Vanderheiden | no | |
Charles LaPierre | no |
Do we want to deprioritize Reminders and messages and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Reminders and messages: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | It is crucial |
Gregg Vanderheiden | no | Again this is good -- but I don't think we should use "requirement" and "require" for an optional tag. |
Charles LaPierre | no |
Do you know of any intended implementations of Reminders and messages? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | |
no | 2 |
(1 response didn't contain an answer to this question)
Responder | Reminders and messages: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | ||
Charles LaPierre | no |
Do we want to deprioritize Distractions and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | |
no | 3 |
Responder | Distractions: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | no | Needs better name? Does anyone actually think what they put in their content is a distraction? Rather than an attraction? this is important but not sure about name and how we would do this. WCAG already talks about animations. Are you talking about anything other than animations? if not -- why not call them that? "Animated content" or "animated content that is not the primary purpose of the page? ?? |
Charles LaPierre | no |
Do you know of any intended implementations of Distractions? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | |
no | 2 |
(1 response didn't contain an answer to this question)
Responder | Distractions: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | |
Gregg Vanderheiden | ||
Charles LaPierre | no |
Do we want to deprioritize New Misc and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | New Misc: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | i think the terms are out there |
Gregg Vanderheiden | yes | Don't understand and there are no details/ is this really an aria role? Role = misc? |
Charles LaPierre | no |
Do you know of any intended implementations of New Misc? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | |
no | 2 |
(1 response didn't contain an answer to this question)
Responder | New Misc: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | not sure |
Gregg Vanderheiden | ||
Charles LaPierre | no |
Do we want to deprioritize Additional WAI-ARIA roles and add an editor’s note explaining our decision?
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 2 |
Responder | Additional WAI-ARIA roles: Prioritization | Comments |
---|---|---|
Lisa Seeman-Horwitz | no | this takes coordination but should be moved from the specification |
Gregg Vanderheiden | yes | good things here - but until we make it a real role |
Charles LaPierre | no |
Do you know of any intended implementations of Additional WAI-ARIA roles? Please add any implementations you know of in the comments section below.
Choice | All responders |
---|---|
Results | |
yes | 1 |
no | 1 |
(1 response didn't contain an answer to this question)
Responder | Additional WAI-ARIA roles: Implementations | Comments |
---|---|---|
Lisa Seeman-Horwitz | yes | I extended aria a few years back and made a reader that used them. i am not sure were it is. Maybe cast is using it. |
Gregg Vanderheiden | ||
Charles LaPierre | no |
The following persons have not answered the questionnaire:
Send an email to all the non-responders.
Compact view of the results / list of email addresses of the responders
WBS home / Questionnaires / WG questionnaires / Answer this questionnaire
w3c/wbs-design
or
by mail to sysreq
.