Skip to content

Create orientation-scroll-reflow-acsmtl - #2446

Draft
WilcoFiers wants to merge 1 commit into
developfrom
orientation-scroll-reflow-acsmtl
Draft

Create orientation-scroll-reflow-acsmtl#2446
WilcoFiers wants to merge 1 commit into
developfrom
orientation-scroll-reflow-acsmtl

Conversation

@WilcoFiers

Copy link
Copy Markdown
Member

First draft of the orientation-scroll-reflow rule: orientation scrolls do not exist at 320 CSS pixels without a content exception.

Split from #2429 so each reflow rule can be reviewed independently. Original work by @HelenBurge.

Related to #2424.

Need for Call for Review:
This will require a 2 weeks Call for Review


Pull Request Etiquette

When creating PR:

  • Make sure you're requesting to pull a branch (right side) to the develop branch (left side).
  • Make sure you do not remove the "How to Review and Approve" section in your pull request description

After creating PR:

  • Add yourself (and co-authors) as "Assignees" for PR.
  • Add label to indicate if it's a Rule, Definition or Chore.
  • Link the PR to any issue it solves. This will be done automatically by referencing the issue at the top of this comment in the indicated place.
  • Optionally request feedback from anyone in particular by assigning them as "Reviewers".
  • If your PR is for a new rule with an Accessibility Support note, or for updating the Accessibility Support note of an existing section, make sure to open a corresponding Accessibility Support issue.

When merging a PR:

  • Close any issue that the PR resolves. This will happen automatically upon merging if the PR was correctly linked to the issue, e.g. by referencing the issue at the top of this comment.

How to Review And Approve

  • Go to the “Files changed” tab
  • Here you will have the option to leave comments on different lines.
  • Once the review is completed, find the “Review changes” button in the top right, select “Approve” (if you are really confident in the rule) or "Request changes" and click “Submit review”.
  • Make sure to also review the proposed Call for Review period. In case of disagreement, the longer period wins.

Made with Cursor

Split from #2429. Original work by Helen Burge.

Co-authored-by: HelenBurge <41951878+HelenBurge@users.noreply.github.com>
@WilcoFiers WilcoFiers added the Rule Use this label for a new rule that does not exist already label Aug 31, 2026
@netlify

netlify Bot commented Aug 31, 2026

Copy link
Copy Markdown

Deploy Preview for act-rules ready!

Name Link
🔨 Latest commit 4e35186
🔍 Latest deploy log https://app.netlify.com/projects/act-rules/deploys/6a9553f88c3abc00083c441a
😎 Deploy Preview https://deploy-preview-2446--act-rules.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@WilcoFiers WilcoFiers mentioned this pull request Aug 31, 2026
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Rule Use this label for a new rule that does not exist already

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants