w3c / wai-bad-demo

Updates to WAI Before and After Demo

wai-bad-demo

Updates to WAI Before and After Demo

wai-bad-demo's Issues

[BAD4Curriculum]

• Overall like the approach
• Should have a quick entry for teachers: What can my students learn? What support material is available?
• I’d like to suggest to provide sample slides for teachers to use.

[BAD] Scope/Redesign?

• A redesign, even “just” coding it responsively, would likely affect most content of the Before After Demo.
• Using the new W3C/WAI layout is probably not a good idea so people don’t get confused.
• The current BAD already already has links to the techniques. I wonder why they need to change to point to the Quickref which then points to techniques.
• I fully support material on how to use BAD in classrooms and other learning environments.

Wishlist: Deep links

It would be good to be able to link into BAD directly, like to the annotations.

via @ericprud and @brewerj

Demo without BAD header

Suggestion by Lewis Phillips via Email:

It would be nice to have the demo code on their own pages without the
header and footer sections. I use the BAD pages to demonstrate testing
tools including some automated tools and it would be helpful to have an
inaccessible page without some valid code at all. The header for example
has an <h1> which means that the page would not fail for missing heading
structure. Maybe have a link to open a page that is only the example?

Suggestion: more interactive, custom UI, JS stack

Comment submitted from the EOWG charter review in June 2017 (W3C member link):

The before/after demo was a useful tool, but it is no longer representative of a modern website (it's too simple, too static, and it's based on a plain HTML stack). We suggest that E/O replace it with something more representative of the modern web platform (more interactive, more custom UI, and based on a JS stack).

Focus indication on radio buttons

Suggestion by Lewis Phillips via Email:

On https://www.w3.org/WAI/demos/bad/after/survey.html the focus indication on the Mr. and Mrs. Radio buttons doesn't work. It looks like the CSS rules do not cover this.

I haven't been able to come up with a rule that will work with the nested within the that will work.

HTML:

<p id="namenewsletter" class="input">
        <label for="mr">Mr. <input type="radio" name="t" id="mr" value="mr" title="title"></label>
        <label for="mrs">Mrs. <input type="radio" name="t" id="mrs" value="mrs" title="title"></label>
        <label for="n">Name: <input type="text" name="n" id="n" size="30" style="margin-left: 0.5em;"></label>
</p>

CSS:

select:focus, select:active, input:focus, input:active, input:focus + label, input:active + label, label[for]:focus, label[for]:active {
  color: #fff !important;
  background-color: #ba2710 !important;
}

Specifically address the accessibility benefits of responsive design

Under:

Notes, issues
• The content of the demo is layered with accessible, inaccessible, and annotated views; may not be possible to use fully responsive design.

I think we should highlight the difference between a site that is not coded to be responsive and one that is responsive increases the accessibility. Therefore only the "after" site should be responsive to highlight the difference. I imagine that is the intent of the note above but could be re-written to be more specific.

This is a test - ignore

Please ignore this issue.

BAD_Curric