Skip to content

Create an "accessible by default" principle. - #616

Open
jyasskin wants to merge 3 commits into
mainfrom
accessible-by-default
Open

jyasskin wants to merge 3 commits into
mainfrom
accessible-by-default

Conversation

@jyasskin

@jyasskin jyasskin commented Jun 2, 2026 •

Copy link
Copy Markdown
Member

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

@matatk matatk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reads very well to me; thanks @jyasskin!

My only change was to use what appears to be the standard capitalisation for JavaScript.

Comment thread index.bs Resolved

@dbaron dbaron left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread index.bs Resolved
@jyasskin
jyasskin force-pushed the accessible-by-default branch from c95949e to 56da5c8 Compare September 17, 2026 23:53
Comment thread index.bs Resolved
Comment thread index.bs
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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Comment thread index.bs Resolved
jyasskin and others added 3 commits November 16, 2026 13:45
Two other principles expressed specific applications of this goal, so I merged them.
Co-authored-by: Matthew Tylee Atkinson <matatk@users.noreply.github.com>
Comment thread index.bs
Comment on lines +328 to +329
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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To address https://github.com/w3ctag/design-principles/pull/616/changes#r3391475050, perhaps:

Suggested change
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.

Comment thread index.bs
Comment on lines +316 to +317
Developers often have limited time
and don't test with all of the options that users will need to choose.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bkardell How about:

Suggested change
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.

@jyasskin
jyasskin force-pushed the accessible-by-default branch from ea05ca5 to e43a379 Compare November 16, 2026 22:00

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants