Repository navigation
Conversation
dbaron
left a comment
There was a problem hiding this comment.
Two thoughts here (along with one other specific comment below):
One, I'm a little worried about the naming of "accessible by default" given the (typically narrower) way the word "accessibility" is generally used in the web technology space. I'm not sure if I have any great answers here.
Second, given the breadth of the principle, I think it would be good to come up with some additional examples. Ideally it would be nice to have a good example about designing for the (narrower definition of) accessibility by default, and maybe about something like designing for operating system independence by default. I don't have any great ones to offer right now, though.
c95949e to
56da5c8
Compare
| with assistive technology to support their individual disabilities. | ||
|
|
||
| Developers often have limited time | ||
| and don't test with all of the options that users will need to choose. |
There was a problem hiding this comment.
I think this should be rephrased. It's not just about limited time, it's limited ability - developers don't have every device, and can't. New devices are introduced that developers could not even in a perfect world have considered because they didn't exist at the time. I'm not sure also what "that users will need to choose" means.
Maybe this is just trying to say
Developers are unable to test with all of the various options that potential users will choose.
But I don't think it's actually necessary? Maybe we can just remove that sentence?
Two other principles expressed specific applications of this goal, so I merged them.
Co-authored-by: Matthew Tylee Atkinson <matatk@users.noreply.github.com>
| For example, the default behavior of all layout systems in CSS will not lead to content being clipped, | ||
| content overlapping other content, or content being unreachable by scrolling. |
There was a problem hiding this comment.
To address https://github.com/w3ctag/design-principles/pull/616/changes#r3391475050, perhaps:
| For example, the default behavior of all layout systems in CSS will not lead to content being clipped, | |
| content overlapping other content, or content being unreachable by scrolling. | |
| For example, the default behavior of all layout systems in CSS | |
| allows users to choose their own screen size, font, and font size | |
| without causing content to be clipped, | |
| overlap other content, or become unreachable by scrolling. |
| Developers often have limited time | ||
| and don't test with all of the options that users will need to choose. |
There was a problem hiding this comment.
@bkardell How about:
| Developers often have limited time | |
| and don't test with all of the options that users will need to choose. | |
| Developers cannot be expected to test with all of the possible choices that a user might make. | |
| Many developers won't even test the variations that spec authors think they _should_ test with. |
ea05ca5 to
e43a379
Compare
The "Media Independence" and "[CSS]Content should be viewable and accessible by default" principles expressed specific applications of this goal, so I merged them.
@dbaron @atanassov, this heavily modifies sections you added, so I'd appreciate a check that I haven't lost anything essential.
Preview | Diff