Support the spec here:
https://docs.google.com/document/d/1YW9BVJypgOE4MjwJiVFwYw8FXiHjyNj-0Et5Jm12q-k/edit#heading=h.fcbi8ziaid5
Or even easier, just support the attached self-describing HTML file.
Note that this is still early and some of the markup may change slightly. This bug will be updated apprpropriately. Please let me know of any implementation challenges caused by the markup.
The overall goal here is to introduce is covering 100% of what Docs needs in order to expose all semantics in Braille mode.
|
Deleted:
proposed-markup.html
3.6 KB
|
Support the spec here:
https://docs.google.com/document/d/1YW9BVJypgOE4MjwJiVFwYw8FXiHjyNj-0Et5Jm12q-k/edit#heading=h.fcbi8ziaid5
Or even easier, just support the attached self-describing HTML file.
Note that this is still early and some of the markup may change slightly. This bug will be updated appropriately. Please let me know of any implementation challenges caused by the markup.
The overall goal here is to introduce is covering 100% of what Docs needs in order to expose all semantics in Braille mode.
Support the spec here:
https://docs.google.com/document/d/1YW9BVJypgOE4MjwJiVFwYw8FXiHjyNj-0Et5Jm12q-k/edit#heading=h.fcbi8ziaid5
Or even easier, just support the attached self-describing HTML file.
Note that this is still early and some of the markup may change slightly. This bug will be updated appropriately. Please let me know of any implementation challenges caused by the markup.
The overall goal here is to introduce is covering 100% of what Docs needs in order to expose all semantics in Braille mode.
The question of whether the role goes on the source or target of aria-details is still up in the air. We might put it on the element with the aria-details, or on the target, don't write a bunch of code either way yet.
Comment 1 Deleted