Instagram UI accessibility changes, dated and checked against WCAG 2.2
Instagram has changed its interface many times since 2018. Here is each change that touches accessibility, with the day it was published and how it holds up against the Web Content Accessibility Guidelines (WCAG) 2.2 on 6 October 2026.
What are the Instagram UI accessibility changes, and do they meet WCAG 2.2?#
Instagram's accessibility changes arrived in dated steps, alt text in 2018, dark mode in 2019 and auto captions in 2022, and none fully settles its WCAG 2.2 criterion. The latest Instagram UI change is the navigation, tested from October 2025. Every verdict below was checked on 6 October 2026 against the W3C's WCAG 2.2 Recommendation, dated 12 December 2024.
So the Instagram UI evolution reads as four steps, and each leaves a gap a product team can learn from.
Show data table
| Item | Value |
|---|---|
| Automatic and custom alt text (28 November 2018) | 94 |
| Dark mode follows the system (8 October 2019) | 83 |
| Auto-generated video captions (1 March 2022) | 55 |
| Reels and DMs navigation test (10 October 2025) | 11 |
Alt text has been live the longest, 94 months, and its gap is still open.
In short, the older a change is, the longer it has had to be fixed. Yet the alt text gap is the oldest, and it is still open.
What changed between the old Instagram UI and the new one?#
The new Instagram UI orders the bottom tabs Home, Reels, DMs, Search and Profile, and moves Create out of the centre into the top left corner. In the Instagram old UI, the tabs were feed, search, create, Reels and profile. For the Instagram new UI, Engadget reported on 10 October 2025 that the test "swaps search and Reels" and lets people swipe between tabs.
| Position | Instagram old UI | Instagram new UI |
|---|---|---|
| 1 | Feed | Home |
| 2 | Search | Reels |
| 3 | Create | DMs |
| 4 | Reels | Search |
| 5 | Profile | Profile |
| Create button | Centre tab | Top left corner |
In that announcement, Instagram head Adam Mosseri said such changes "can take time to get used to". Then Social Media Today reported on 19 October 2025 that more people were being offered the new UI. By March 2026, Storrito wrote that the redesigned bar is fixed and cannot be rearranged.
For accessibility, this Instagram interface change raises two questions. First, every target moved, so muscle memory breaks for anyone who taps by position. Second, a corner button is harder to reach with one thumb.
24
Target Size (Minimum), Level AA (2.5.8)
44
Target Size (Enhanced), Level AAA (2.5.5)
A moved button must still clear 24 CSS pixels per side to meet Level AA.
| Option | CSS pixels per side |
|---|---|
| Target Size (Minimum), Level AA (2.5.8) | 24 |
| Target Size (Enhanced), Level AAA (2.5.5) | 44 |
Source: W3C, WCAG 2.2, 2024
So a moved button must still pass the floor. Android's accessibility guide, read on 6 October 2026, asks for touch targets of "at least 48dpx48dp", above both WCAG levels.
Does Instagram's alt text meet WCAG 2.2 success criterion 1.1.1?#
Custom alt text can meet success criterion 1.1.1, but automatic alt text lists the objects a photo may contain rather than the purpose the photo serves. Instagram announced both on 28 November 2018. Its announcement cited "more than 285 million people in the world who have visual impairments".
That post said the automatic version lets people "hear a list of items that photos may contain". The Instagram Help Center, read on 6 October 2026, still says "Automatic alt text uses object recognition technology". It adds that you can replace the text.
However, WCAG 2.2 asks for a text alternative that serves the same purpose as the image. For example, a list such as "people, outdoors" rarely tells anyone why the photo was posted. The W3C's Understanding Non-text Content page explains that purpose test. So the automatic text is a fallback, and the custom field is the part that can pass.
So ask for alt text at upload, while the person posting still knows what the image is for.
Is Instagram dark mode an accessibility feature?#
Dark mode on Instagram is a display preference, not an accessibility fix, because WCAG 2.2 asks for 4.5:1 text contrast whichever theme is showing. Techweez reported on 8 October 2019 that Instagram dark mode arrived with iOS 13 and Android 10. It was tied to the phone's system setting.
That tie still holds, and the Instagram dark mode help page, read on 6 October 2026, says "Dark mode cannot be turned on or off in the Instagram app for iPhone". Instead, it points to the device settings. On Instagram.com, the same page says to click More, then Switch appearance.
Some people prefer a dark theme, but neither theme raises contrast by itself. Therefore the WCAG test is the same in both themes. The W3C's WCAG 2.2, dated 12 December 2024, says text needs "a contrast ratio of at least 4.5:1".
Show data table
| Item | Value |
|---|---|
| Body text, Level AA (1.4.3) | 4.5 |
| Large text, Level AA (1.4.3) | 3 |
| Body text, Level AAA (1.4.6) | 7 |
| Large text, Level AAA (1.4.6) | 4.5 |
| Icons and controls, Level AA (1.4.11) | 3 |
Body text needs 4.5:1 at Level AA in either theme, and large text and icons need 3:1.
For example, take an illustrative grey, #737373. In our 6 October 2026 check with the WCAG 2.2 contrast formula, it scores 4.74:1 on white and passes. But on a near-black #121212 background, the same grey scores 3.95:1 and fails for body text.
4.83:1 on light #FFFFFF
PassBody text needs 4.5:1
- Body text at 4.5:1Pass
- Large text and icons at 3:1Pass
#6B7280 passes body text here but fails on dark #121212 at 3.87:1, so this token flips between themes.
Computed from the WCAG 2.2 relative luminance and contrast ratio definitions. The ratio is cut to two decimals, never rounded up.
In practice, a team that ships a dark theme must check every colour pair twice, once per theme.
Do Instagram's auto-generated captions meet the WCAG 2.2 captions rule?#
Auto-generated captions, reported by TechCrunch on 1 March 2022 in 17 languages, help deaf and hard of hearing viewers, but WCAG 2.2 counts only captions that match the audio. TechCrunch wrote that "auto-generated captions are launching in 17 languages". Viewers can turn them on or off.
Success criterion 1.2.2 asks for captions on prerecorded video. The W3C's Understanding Captions page says captions carry spoken dialogue and "equivalents for non-dialogue audio information". But a machine transcript can mishear a name or skip a sound cue. When it does, it is no longer an equivalent.
As a result, the creator's review is the accessibility step. So a product team that adds auto captions should prompt the uploader to read and correct them before the video goes live.
The machine draft
Auto-generated captions, reported by TechCrunch on 1 March 2022 in 17 languages, turn the speech into text.
The 1.2.2 test
Captions must carry spoken dialogue and equivalents for non-dialogue audio information, per the W3C Understanding Captions page.
The creator's review
The uploader reads and corrects them before the video goes live, so a misheard name or a skipped sound cue is fixed.
Does Instagram scale text and respect reduced motion?#
Instagram hands text size to the phone or browser setting, which can satisfy success criterion 1.4.4 at 200 percent if every layout survives the zoom. The W3C's WCAG 2.2, dated 12 December 2024, says text should resize "up to 200 percent without loss of content or functionality".
The text size help page, read on 6 October 2026, says "You can change text size on Instagram through your device or browser settings." Since people set their size once for every app, leaning on the system is a sound choice. Still, the test is whether captions, buttons and comments fit at the largest setting.
Motion is the gap, because the new navigation lets people swipe between tabs and each swipe moves the whole screen. So success criterion 2.3.3 applies, the same criterion a reduced-motion guard for anime.js animations supports. The W3C's Understanding Animation from Interactions asks that "Motion animation triggered by interaction can be disabled". Yet none of the Instagram help articles read on 6 October 2026 mention a reduce motion setting.
| WCAG 2.2 criterion | What Instagram's help pages say | Verdict on 6 October 2026 |
|---|---|---|
| 1.4.4 Resize Text, up to 200 percent | Text size follows the device or browser settings | Can pass, if captions, buttons and comments fit at the largest setting |
| 2.3.3 Animation from Interactions | No reduce motion setting is mentioned | The gap: each swipe between tabs moves the whole screen |
What do screen reader users report about Instagram's interface?#
VoiceOver users on the AppleVis forum reported through July 2026 that Stories stickers, video sound and notification settings stopped working with the screen reader. One user wrote that the app was accessible "almost perfectly before April 2026". The same user added that "as of July31, 2026, the issue is still there" in the AppleVis thread.
- Before April 2026
Accessible almost perfectly
One VoiceOver user wrote that the app was accessible "almost perfectly before April 2026".
- April to July 2026
Controls stop working with VoiceOver
Users reported that Stories stickers, video sound and notification settings stopped working with the screen reader.
- 31 July 2026
Still not fixed
The same user added that "as of July31, 2026, the issue is still there". The thread names no fix date.
These are user reports, not a test, and the thread names no fix date. Still, they map onto success criterion 4.1.2. The W3C's Understanding Name, Role, Value asks that "the name and role can be programmatically determined" for every control. So a settings button that VoiceOver cannot press fails that test.
Android's guide, read on 6 October 2026, sets the same rule for its platform. It asks for a contentDescription on any control without visible text. In short, a redesign can break labels that worked the week before, so they need a test after every release.
When is Instagram the wrong fit as an accessibility model?#
Instagram is the wrong model when a product cannot lean on phone settings and object recognition, because its approach delegates text size and image descriptions to them. Then a different route helps more.
- A web app with custom text controls. If your layout sets its own font sizes, phone settings will not reach it. Test zoom to 200 percent against success criterion 1.4.4 in the W3C's WCAG 2.2, dated 12 December 2024.
- A product with no image recognition model. Do not copy automatic alt text. Instead, make a written description a required field at upload, which is the part of Instagram's design that can pass 1.1.1.
- A small team shipping one app. Copying a large app's navigation copies its retraining cost too. Start from the 48dp touch target in Android's guide, read on 6 October 2026, and the WCAG 2.2 target size rule.
| Case | Why Instagram's pattern does not transfer | Check to use instead |
|---|---|---|
| A web app with custom text controls | Phone settings will not reach a layout that sets its own font sizes | Test zoom to 200 percent against 1.4.4 |
| A product with no image recognition model | There is no automatic alt text to copy | Make a written description a required field at upload (1.1.1) |
| A small team shipping one app | Copying a large app's navigation copies its retraining cost too | Start from the 48dp touch target and the WCAG 2.2 target size rule |
What can a product team learn from Instagram's accessibility changes?#
Each Instagram change teaches one rule: prompt for alt text at upload, test contrast in both themes, review captions, respect system text size and re-test labels after every redesign. These are the WCAG 2.2 checks the Instagram UI accessibility changes touch, and good Instagram user interface design has to pass them too.
Also check target size. Under the W3C's WCAG 2.2, dated 12 December 2024, a target needs 24 by 24 CSS pixels at Level AA. So every moved button should be measured again.
Where to go next on accessible interface design#
For the checks behind this review, the contrast, screen reader and captions guides go deeper than any single app can show. The guide to colour contrast accessibility covers how to measure and fix each pair. For labels, see screen reader compatibility testing. For captions and audio description, read accessible multimedia, and for design work, WCAG in UI and UX design.
If you want your own interface checked, the accessibility testing and WCAG and ADA compliance pages describe how that works. But the W3C's WCAG 2.2 Understanding pages are enough on their own to run every check above.