Skip to content

Create an "accessible by default" principle.#616

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

Create an "accessible by default" principle.#616
jyasskin wants to merge 2 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

Two other principles expressed specific applications of this goal, so I merged them.

@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 Outdated

@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

<div class="example">
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

Choose a reason for hiding this comment

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

I think it might be worth mentioning possible causes of such problems, which include both variation in screen size and variation in user settings like font sizes. (That was more explicit in one of the two examples, the block/flex/grid one, that you merged into this one.)

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.

@dbaron could you suggest how you'd prefer to fix this?

Co-authored-by: Matthew Tylee Atkinson <matatk@users.noreply.github.com>
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