ibma / va11ys Goto Github PK

The titles and h1 of each technique page should be updated to match their link text on their index page.

Just wondering why the square brackets around the asterisk for the required fields. I've never seen anyone implement it that way before. Why not just the asterisk?

I'll be testing ARIA1 - ARIA6 on Android

Work with DAP team on how they can use the component start / end as test cases

Added Android TalkBack for HTML32 1 and 2

On such short pages, I do not think you need a banner. Unless you have some good reason for wanting to put in a banner, I would consider making the page start with main and put the navigation region at the BOTTOM of the main region, maybe with a label of "breadcrumb".
This is just a suggestion to investigate. I just found when doing testing with JAWS that having a banner and navigation preceding what I wanted to work with was just noise. If the navigation followed, I could hear the sample then just tab once more to get back to a prior location.

Repo needs to house WCAG techniques and then other samples not directly from WCAG. Currently WCAG techs are in /HTML /ARIA /GENERAL etc.

A better dir structure would have been something like: /wcag_html_techs/ and then /html/ for others. Need to create:
/wcag_html_techs/
/wcag_aria_techs/
/wcag_general_techs/
/html/
/aria/
etc

Will need to up move existing files and update all of the breadcrumbs and links. :-o

Hi Marc,
Just want to let you know that I ran cloc over ta11y today. The current LOC is 2913.

ta11y.loc.txt

Regards,
Moe

A non-functioning submit button is a bit confusing. I assume you've just put it in there to avoid some DAP error. How about naming it "this submit button does nothing" etc, if you feel it has to be there.

Just noticed this error on https://ibma.github.io/Va11yS/WCAG_ARIA/ARIA18_example1.html:

Uncaught ReferenceError: $ is not defined at ARIA18_example1.html:11

Example:

<code style=display:block;white-space:pre-wrap>
<a href="extras/products.html">
    <img src="img/icon.gif" alt=""> Products page
</a>
</code>

I would expect to have the tooltip appear on hover, but it is only appearing on the screen on focus then disappearing when I hover over it, and it doesn't come back.
This isn't a real implementation of tooltip, and I think it should behave just like one. It seems to me there are a couple of things you're blending together here. One is a visible tooltip via keyboard. The other is a tooltip announced by JAWS. I would suggest you scrap the the first one (keyboard triggered tooltip) as being outside the scope of this example. You can notate that, and give this technique as an example later, but it's muddying the water.