Confirm
681
edits
Changes
update
==== ChangeLog ====
* 2015/5/8 gaia-button change from Not Ready to Can Use state
== Gaia Components Basic Treatments ==
=== Visual ===
The elements UX and visual should be correct, please contact Harly (hhsu@mozilla.com, UX) or
Przemek (pabratowski@mozilla.com, UI) for prove.
=== RTL ===
There's theme-selector in each component's exmaple page. Use it to check RTL support status and think about what can be supported by the component itself.
=== Syntax ===
Basic lint and unit test is required. Run `npm run lint` for link check, run `npm test` for unit test.
=== Performance ===
Create a local web server and browse your FxOS device to `http://localhost:8000/test/stress.html`. Make sure you measure the performance with real device. Or the result will not really useful.
=== Accessibility ===
Most of accessibility(a11y) enhancements could be pre-defined by component designer. The component user could benifit from a11y automatically.
To enable screen reader on FxOS, tap up then down button trice. then tap up then down button trice again.
The component should inherit proper role of aria.
http://rawgit.com/w3c/aria/master/aria/aria.html
For example, button should have `role=button`.
The current name or state should be exposed to ScreenReader as well. For example, button should have `aria-checkd="true" aria-disabled="true"` when button is checked and disabled.
