Accessibility statement

What we have done 

Some of our recent accessibility improvements

• Enhanced appearance of alternative text (alt text) 
• Enhanced heading structure 
• Enhanced content structure to follow proper HTML standards 
• Enhanced color contrasts 
• Enhanced keyboard navigation and focus states 
• Enhanced usage of aria labels 
• Enhanced landmark roles (made with ARIA) 
• Enhanced descriptive accessible names for buttons and links 
• Better support for visual updates to be announced to assistive technology 
• Added skip links option 
• Hidden decorative videos from assistive technologies  

• Added alt texts to key images (e.g., Digital Key, Car in Use) 
• Improved screen reader support for visual-only elements (e.g., step indicators, climate settings) 
• Improved contrast and clarity in UI components 
• Ensured proper naming of buttons and labels 
• Improved focus handling and tab order 
• Adjusted spacing between interactive elements 
• Coded links and buttons correctly for assistive technologies 
• Clarified unclear button labels (e.g., 'Change Car', 'Settings') 
• Corrected heading structures for screen readers 
• Added accessibility labels or traits to key interactive elements 
• Ensured proper focus behavior in modals and dialogs 
• Improved screen reader compatibility for dynamic UI components 
• Split long texts into readable paragraphs 
• Fixed VoiceOver crashes during scrolling 
• Corrected semantic markup for headings 
• Max charge limit indicators are not announced by screen readers 

How we work with accessibility

How we continuously improve

How do I report accessibility issues? 

List of non-conformant guidelines

Polestar.com

• Images lack alternative text (alt text) or have unclear descriptions. 

• Videos lack subtitles. 
• Decorative videos aren’t hidden from assistive technologies. 

• Some pages lack proper heading structure or use headings incorrectly. 
• Landmark roles (made with ARIA) are missing or not correctly implemented. 
• Content structure doesn't follow proper HTML standards. 

• Some content lacks proper contrast or uses color incorrectly. 
• Zooming or adjusting text spacing may cause minor display issues. 

• Keyboard focus occasionally gets stuck. 
• Page navigation sometimes lacks logical order. 
• Some content isn't keyboard accessible. 

• Skip links are not correctly implemented. 
• Some guidance content is unclear or inconsistent (e.g, page titles, link purpose, labels). 
• Interactive elements have poor focus visibility. 

• Some elements have inconsistent visible text and accessible names. 

• Language tags are missing or wrong, affecting screen readers. 

• Unexpected content updates affect user focus. 
• Forms are inconsistently implemented. 

• Certain input fields have no labels or instructions. 

• Buttons and links lack descriptive accessible names or are not provided in the local language. 
• Not all visual updates are announced to assistive technology. 
• Error messages are missing or appear unexpectedly. 
• Error messages don’t explain what went wrong or how to resolve it. 

• User settings may not apply properly or cause display issues. 

• Some PDFs are not fully accessible. 

Who is affected

• Users with visual impairments, who rely on screen readers or magnification tools, may be affected by insufficient contrast and the absence of alternative text, and have issues to navigate due to incorrect structure of the content. 
   
• Users with hearing impairments, who require captions for video content, may be affected when videos lack subtitles. 
   
• Users with motor impairments, who navigate using a keyboard or other assistive devices, may encounter difficulties to access some buttons and links and issues with tab order, focus indicators and inconsistent form behavior. 
   
• Users with cognitive disabilities may struggle to understand the content when clear labels, instructions, or a logical page structure are missing. 

Polestar iOS App 

• Some images lack alternative text (alt text) or have unclear descriptions. 
• Information conveyed by graphic does not provide a text alternative. 

• Some views lack proper heading structure or use headings incorrectly. 
• Some content is not properly structured semantically. 

• Some Color contrasts are insufficient for text and icons. 
• Input fields and visual indicators lack sufficient contrast. 
• Text resizing does not work consistently across the app. 

• In a rare case, the focus gets trapped. 

• The focus order is sometimes illogical or misleading. 

• The target size on interactive elements are sometimes too small and causes the risk of activating unexpected actions. 

• Some error messages are vague or unclear. 

• Buttons and toggles are vaguely named or unnamed   
• Some interactive elements don't convey their role. 
• Changes in content/status are not conveyed to technical aids. 

• App crashes or does not behave correctly with VoiceOver. 
• Missing support for native gestures like back/cancel. 

Who is affected 

• Users with visual impairments, who rely on screen readers or magnification tools, may be affected by missing or unclear text alternative for images and graphics. They may also be affected by insufficient color contrast in text, icons, input fields, and visual indicators, as well as inconsistent text resizing support across the app. 
   
• Users with motor impairments may experience difficulties with navigation due to focus being trapped, illogical focus order, small or inconsistently responsive interactive elements, and missing support for native gestures like back or cancel. 
   
• Users with cognitive disabilities may struggle when error messages are vague or unclear, or when content lacks proper semantic structure and clear heading hierarchy. 
   

Polestar Android App 

• Some images lack alternative text (alt text) or have unclear descriptions. 
• Information conveyed by graphics and animations does not provide a text alternative. 

• Some views lack proper heading structure or use headings incorrectly. 
• Some content is not properly structured semantically. 
• Some content doesn’t provide contextual meaning for assistive tech. 
• Some components have no, or unclear accessible names. 
• no support for landscape orientation. 

• Error messages rely on color alone to indicate an issue, without visual cues such as icons or symbols. 
• Some Interactive elements are not visually distinguishable from other content and lack visual cues (outlines, background color). 

• Focus order is sometimes incorrect or lands on visually hidden content, causing an unclear navigation experience. 
• Some buttons lack clear visual labels and accessible text. 
• Some names of labels and buttons are not translated to the chosen language. 

• There are no alternatives to swipe gestures, such as buttons, to navigate. 

• Some instructions are incorrect or unclear. 

• Buttons are missing correct name, role, and value. 
• No state information, such as expanded/collapsed, selected is provided. 
• Some non-clickable elements are incorrectly marked as clickable. 
• Contextual information such as name and number of pages in carousel are not announced. 
• Some elements names are presented as “null”. 
• Some interactive components such as dropdowns are not properly implemented for usage with assistive tech. 
• Some feedback is not announced to assistive tech. 

Who is affected

• Users with visual impairments may be affected by missing or unclear text alternative for images and graphics. Missing or incorrect semantic structure, such as headings and labels, can affect navigation with screen reader. Missing state information and vague or incorrect button names can cause issues with navigation with assistive technologies. Reliance on color alone and lack of visual indicators for interactive elements also reduce accessibility for users with low vision or color blindness. 
  
  
• Users with motor impairments who can’t rely on swipe gestures cannot use al functionality. Incorrect focus order, small or visually ambiguous buttons, and poorly implemented dropdowns can make the interface difficult or impossible to operate without precise touch or fine motor control. 
  
  
• Users with cognitive disabilities may struggle when error messages are vague, instructions are unclear, or buttons and content lack consistent labeling and structure.