Comments (1)
@justinfagnani Thanks for the suggestion. While I agree in general, this is a tricky thing to get right.
- Everyone will have different ideas about what's important.
- History has shown that people are tempted to assign a high priority to issues that affect them directly, and low priority to issues that don't affect them. This is particularly true of accessibility concerns.
- If a developer's goal is to get their component adopted, aesthetic concerns may be just as big barriers to adoption as the correctness of all low-level details. I've seen otherwise interesting components on Bower with such idiosyncratic visual presentations that they couldn't be used on most sites without substantial modification. While it's easy enough to say that adopters should just feel free to style the component they way they want, in practice most people will just look elsewhere for a component they can use without modification. A dev might be better off fixing that presentation before tackling reattachment.
That said, I agree that this list may overwhelm people. I think experience will be the best guide in determining which checklist items are most critical βΒ the ones that are the most important to get right and/or which people most often forget to address. So I think it might be helpful to give this list some time before trying to assign levels of priority. For now, my focus is on getting the list correct, and backing up all recommendations with detail, sample code, and other resources.
from gold-standard.
Related Issues (18)
- Recommendations for generating change events when an attribute has updated? HOT 25
- Feedback HOT 4
- Clarify/refine Relative Paths HOT 1
- Clarify/refine Local Effects HOT 1
- Clarify Child Independence
- Refine Back-End Independence
- Clarify Responsive guideline
- Clarify Progress Feedback guideline
- Bug in examples: Uncaught SyntaxError: await is only valid in async function HOT 2
- Duplicate checklist item: Child independence HOT 1
- [WIKI] Declared Semantics contains dead links to Aria HOT 1
- Needs something about style separation HOT 1
- Naming & namespacing HOT 6
- Consider adding an item to address validation of input elements
- Potential Logo for Adherence HOT 2
- Tools for enforcing the gold-standard? HOT 4
- Gold standards should include unit tests
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gold-standard.