-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should <dir> behave like a list element? #9296
Comments
That page doesn't seem to mention the |
Deprecated/obsolete features aren't listed in HTML AAM. In this case, the element was deprecated/made obsolete years before AAM was created. I could add those into the spec, but with rare exceptions like the dir element (where it says it should be treated like a UL, so it should be mapped to role=list), many of these features will have no useful mappings for accessibility. |
@Ahmad-S792 recently made the rendering match the spec / Firefox in WebKit/WebKit@5febb62 |
The visual impact of alternating the marker for nested lists is likely inconsequential since Running a query of 1% of httparchive I found 7 pages using Mapping to QueryTotal number of pages is 12,890,459; this runs on a 1% sample subset.
Result
|
I guess I don't care strongly which way this goes. Aligning everything with the HTML Standard, including HTML AAM, works too. |
Filed w3c/html-aam#486 |
Only Gecko seems to render http://software.hixie.ch/utilities/js/live-dom-viewer/?%3Cdir%3E%3Cli%3Etest%3Cdir%3E%3Cli%3Etest as HTML asks for.
That makes me think that at this point it's probably more web compatible to not do that.
https://w3c.github.io/html-aam/ also doesn't map it to role=list it seems.
cc @zcorpan @mfreed7
The text was updated successfully, but these errors were encountered: