Horizontal scrolling content at a height equivalent to 256 CSS pixels, which is equal to a starting viewport height of 1024 CSS pixels at 400% zoom。

水平滚动内容的高度等于256 CSS像素 ，等于400％缩放时起始视口高度为1024 CSS像素。

Exemptions are available for images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content are exempt。 That exemption list is not as long as it sounds。 Most static and dynamic pages do not qualify。

豁免适用于图像，地图，图表，视频，游戏，演示文稿，数据表和界面，其中在操作内容时必须保持工具栏处于可见状态。 该豁免清单听起来并不长。 大多数静态和动态页面均不合格。

Hmmm absolute pixel values that a developer / designer can define in CSS to get the optimal user experience — what does that sound like?

开发人员/设计人员可以在CSS中定义的Hmmm绝对像素值，以获得最佳的用户体验-听起来像什么？

Oh yeah, RESPONSIVE BREAKPOINTS!

哦，是的，React力很强！

The guideline is called Reflow because the requirement is that the design re-organizes itself when someone zooms in up to 4X。 But in actuality, it would have been more accurate to call it Responsive, because the way to implement that is *exactly* how you would implement responsive breakpoints。

该准则称为“重排”，因为要求是当有人放大到4倍时，设计必须重新组织。 但实际上，将其称为“响应式”会更准确，因为实现的方法是“精确地”实现响应式断点的方式。

— make it bigger

—加大

— re-organize the elements around the larger font sizes

—重新组织大字体周围的元素

— don’t make it hard for people to get around

-不要让人们四处走动

By the way, if you are meeting the new guideline 1。4。10, you are probably inherently meeting 1。4。4

顺便说一句，如果您要满足新的准则1。4。10，则可能天生就符合1。4。4。

These are Level AA guidelines。 I’ve heard people refer to Level AA as “nice to have。” They aren’t。 Unless your company is in Ontario Canada only for Ontarians and is shutting down in five months, if there is an accessibility law, Level AA is required。 Level AA is not as crucial as Level A, because Level A issues are blockers。 That doesn’t mean Level AA isn’t essential!

这些是AA级指南。 我听说有人称AA级为“很不错”。 他们不是。 除非您的公司仅在安大略省的加拿大安大略省开张，并且要在五个月内关闭，否则如果有无障碍法律，则要求AA级。 A级问题没有A级问题那么重要，因为A级问题是阻碍因素。 这并不意味着AA级不是必不可少的！

1。4。4 and 1。4。10 are the guidelines that most likely trigger whining about how expensive being accessible is。 Well, sure accessibility is going to be costly if you are doing it reactively (i。e。, if you are trying to jam it in after all your design and development work is done)。 The vast majority of accessibility fixes are simple; five lines of code or less。 Magnification fixes do not come in the “simple” category。 Proactive accessibility where you design and code your digital property to be accessible; it is a less expensive approach that results in a better product with fewer bugs that will more likely hit your release dates。 Starting with an accessible design system like Clarity will help save you time。 Don’t reinvent the wheel if you don’t have to。

1。4。4和1。4。10是最有可能引发抱怨的问题，即可访问性的价格是多少。 好吧，如果您以被动的方式进行可访问性(例如，如果在完成所有设计和开发工作后试图将其卡住)，那么可访问性肯定会很昂贵。 绝大多数可访问性修补程序都很简单； 五行或更少的代码。 放大倍率修复程序不在“简单”类别中。 在您设计和编码数字资产以使其可访问时的主动可访问性； 它是一种较便宜的方法，可以使产品更好，错误更少，而这些错误更有可能会影响您的发布日期。 从诸如Clarity之类的可访问设计系统开始，将帮助您节省时间。 如果没有必要，不要重新发明轮子。