From faeee1ef3b83fac95d1a6ac5065bd69c9b8f6bd1 Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Mon, 1 Jun 2026 21:20:32 -0700 Subject: [PATCH 1/3] Create an "accessible by default" principle. Two other principles expressed specific applications of this goal, so I merged them. --- index.bs | 67 ++++++++++++++++++++++++++------------------------------ 1 file changed, 31 insertions(+), 36 deletions(-) diff --git a/index.bs b/index.bs index 8bd62f44..e7f1ec9e 100644 --- a/index.bs +++ b/index.bs @@ -297,20 +297,40 @@ necessary. Use short-lived, temporary identifiers unless a persistent identifier is absolutely necessary. -

Support the full range of devices and platforms (Media Independence)

- +

Content should be accessible by default

-As much as possible, -ensure that features on the web work across different input and output [devices, -screen sizes, interaction modes, platforms, and media](https://www.w3.org/TR/ethical-web-principles/#multi). +An inattentive developer should, by default, +produce content that the widest possible set of users can interact with, +whether or not they have the [[ethical-web-principles#multi|devices, software]], +or [[ethical-web-principles#allpeople|abilities]] that the developer tested against. +That is, the simplest ways to use HTML, CSS, and Javascript should produce content that is +[[wcag22#perceivable|perceivable]], [[wcag22#operable|operable]], and [[wcag22#robust|robust]]. One of the main values of the Web is that it's extremely flexible: -a Web page may be viewed on virtually any consumer computing device -at a very wide range of screen sizes, -may be used to generate printed media, -and may be interacted with in a large number of different ways. -New features should match the [existing flexibility](https://www.w3.org/TR/ethical-web-principles/#render) -of the web platform. +a user can choose to view a web page on +almost any device (including paper), interaction modality, and screen size, +using browsers that make a range of interface choices, +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. +Design features to preserve and improve +the [[ethical-web-principles#render|existing flexibility]] +and accessibility of the web platform, +even when used by hasty developers. + +It should take sophistication and non-default attributes, properties, and arguments +to create pages that exclude some users, +rather than requiring sophistication to include everyone. + +
+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. +These things should only happen if CSS features are used that are more explicitly choosing +such a behavior (for example, `overflow: hidden` or `left: -40em`). They should not happen by +default as a result of something like `display: flex` or `position: relative`. +
This doesn't imply that features which don't work in *every* possible context should be excluded. @@ -323,18 +343,6 @@ and can be adapted to devices that don't support their original intent - for example, a tap on a mobile device will fire a ''click'' event as a fallback.
-Features should also be designed so that the easiest way to use them -maintains flexibility. - -
-The 'display: block', -'display: flex', -and 'display: grid' layout models in CSS -all default to placing content within the available space and without overlap, -so that it works across screen sizes, -and allows users to choose their own font and font size without causing text to overflow. -
- Sometimes features aren't yet available on some implementations or platforms despite working on others. In these cases, features should be designed such that it is possible for @@ -1517,19 +1525,6 @@ since properties are generally setting a mode or state. See [[#naming-is-hard]] for general (cross-language) advice on naming. -

Content should be viewable and accessible by default

- -Design CSS properties or CSS layout systems (which are typically values of the `display` property), -to preserve the content as viewable, accessible and usable by default. - -
-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. -These things should only happen if CSS features are used that are more explicitly choosing -such a behavior (for example, `overflow: hidden` or `left: -40em`). They should not happen by -default as a result of something like `display: flex` or `position: relative`. -
-

JavaScript Language

Use JavaScript for Web APIs

From 0e751bf0a2ac20493ba6ed8e0d7201856b57c3b5 Mon Sep 17 00:00:00 2001 From: Brian Kardell Date: Wed, 8 Jul 2026 13:12:19 -0400 Subject: [PATCH 2/3] Update index.bs Co-authored-by: Matthew Tylee Atkinson --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index e7f1ec9e..08bd5d3d 100644 --- a/index.bs +++ b/index.bs @@ -304,7 +304,7 @@ An inattentive developer should, by default, produce content that the widest possible set of users can interact with, whether or not they have the [[ethical-web-principles#multi|devices, software]], or [[ethical-web-principles#allpeople|abilities]] that the developer tested against. -That is, the simplest ways to use HTML, CSS, and Javascript should produce content that is +That is, the simplest ways to use HTML, CSS, and JavaScript should produce content that is [[wcag22#perceivable|perceivable]], [[wcag22#operable|operable]], and [[wcag22#robust|robust]]. One of the main values of the Web is that it's extremely flexible: From e43a379660c3f884311cc2298dd3759df83d553a Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Tue, 6 Oct 2026 17:17:20 -0700 Subject: [PATCH 3/3] "accessible and widely usable" --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index 08bd5d3d..55f8e611 100644 --- a/index.bs +++ b/index.bs @@ -298,7 +298,7 @@ Use short-lived, temporary identifiers unless a persistent identifier is absolutely necessary.

Content should be accessible by default

+ id="accessible-by-default">Content should be accessible and widely usable by default An inattentive developer should, by default, produce content that the widest possible set of users can interact with,