Polestar努力保障每一个人的数字可访问性。
Polestar努力保障每一个人的数字可访问性。
我们投入大量精力并将Web内容可访问性指南 (WCAG) 2.1 AA级标准用作指南,以确保残障人士能够以独立和平等的方式使用本网站并享受本网站服务。
我们投入大量精力并将Web内容可访问性指南 (WCAG) 2.1 AA级标准用作指南,以确保残障人士能够以独立和平等的方式使用本网站并享受本网站服务。
我们认识到本网站的某些部分尚不是完全可访问的,但我们一直致力于改善本网站的可访问性功能。
我们认识到本网站的某些部分尚不是完全可访问的,但我们一直致力于改善本网站的可访问性功能。
本可访问性声明介绍我们当前的可访问性状态,我们将随着合规工作的开展持续更新本声明。
本可访问性声明介绍我们当前的可访问性状态,我们将随着合规工作的开展持续更新本声明。
我们所做的工作
我们定期审核网站,以发现问题并改善其可访问性。我们与外部审核员合作,集中精力优先解决最关键的问题。我们努力遵循WCAG 2.1的指导原则,这些指导原则在我们的一切工作中具有可感知性、可操作性、可理解性和稳健性,我们的目标是尽可能完全符合WCAG 2.1 AA级标准。
我们定期审核网站,以发现问题并改善其可访问性。我们与外部审核员合作,集中精力优先解决最关键的问题。我们努力遵循WCAG 2.1的指导原则,这些指导原则在我们的一切工作中具有可感知性、可操作性、可理解性和稳健性,我们的目标是尽可能完全符合WCAG 2.1 AA级标准。
我们最近的一些可访问性改进包括:
我们最近的一些可访问性改进包括:
- 从技术上可以为图像提供替代文本
- 更新标题结构,以便清 楚正确地标记标题。
- 明确指示网站上显示的重点内容
- 选项卡顺序改善
- 能够暂停自动播放视频
- 可从技术层面在控件上设置Aria标签
- 在表单页面中显示错误消息
- 在页脚等中插入地标
我们如何保障可访问性
我们的目标是构建一个让所有人都可以访问的网站。为此,我们在网站开发过程中不断进行测试,并每年进行多次手动审核。对于自动化测试,我们使用HTML验证器、浏览器和编辑器插件。
我们的目标是构建一个让所有人都可以访问的网站。为此,我们在网站开发过程中不断进行测试,并每年进行多次手动审核。对于自动化测试,我们使用HTML验证器、浏览器和编辑器插件。
我们支持Firefox、Microsoft Edge、Safari和Chrome浏览器的两大最新版本。
我们支持Firefox、Microsoft Edge、Safari和Chrome浏览器的两大最新版本。
尽管如此,我们意识到可能仍无法在任何给定的时间通过所有可用的在线验证工具。请在下方查看我们有关如何实现改善客户体验这一目标的策略,以及有待进一步处理的当前所有已知问题的列表。我们预计这些问题将作为开发积压工作的一部分在网站重新设计的未来更新中得到解决。
尽管如此,我们意识到可能仍无法在任何给定的时间通过所有可用的在线验证工具。请在下方查看我们有关如何实现改善客户体验这一目标的策略,以及有待进一步处理的当前所有已知问题的列表。 我们预计这些问题将作为开发积压工作的一部分在网站重新设计的未来更新中得到解决。
我们如何持续改进
我们不断识别和记录在网站上发现的任何可访问性问题,并根据它们对访客的总体影响以及解决这些问题所需的工作量确定优先级。从可访问性的角度来看,我们会立即解决对网站体验具有重大影响的问题。我们采取合理措施并在上次审核后6个月内解决其他问题。
我们不断识别和记录在网站上发现的任何可访问性问题,并根据它们对访客的总体影响以及解决这些问题所需的工作量确定优先级。从可访问性的角度来看,我们会立即解决对网站体验具有重大影响的问题。我们采取合理措施并在上次审核后6个月内解决其他问题。
如果您在浏览我们的数字资产时遇到可访问性问题,请通过accessibility@polestar.cn联系Polestar支持部门。
如果您在浏览我们的数字资产时遇到可访问性问题,请通过accessibility@polestar.cn联系Polestar支持部门。
请放心,我们会认真对待您的反馈,并在评估满足所有客户需求的方法时予以考虑。
请放心,我们会认真对待您的反馈,并在评估满足所有客户需求的方法时予以考虑。
有关我们处理您个人数据的信息,请阅读我们的隐私声明。
有关我们处理您个人数据的信息,请阅读我们的隐私声明。
我们的目标是尽可能符合WCAG 2.1 AA级标准。我们的工作目前仍在进行中,以满足以下所载明的原则。
我们的目标是尽可能符合WCAG 2.1 AA级标准。我们的工作目前仍在进行中,以满足以下所载明的原则。
指导原则 1.1 替代文本
1.1.1 非文本内容
指导原则 1.1 替代文本
1.1.1 非文本内容
- 并非所有页面中都提供替代文本。
- 替代文本主要以英语而非当地语言提供。
指导原则 1.2 时基媒体
指导原则 1.2 时基媒体
- 某些视频缺少字幕/替代文本。
- 某些视频缺少作为装饰性视频所具备的信息。
指导原则 1.3 可调整
1.3.1 信息和关系
指导原则 1.3 可调整
1.3.1 信息和关系
- 有些页面没有清晰的标题结构。
- 一些不必要的Aria使用。
1.3.2 有意义的顺序
1.3.2 有意义的顺序
- 这适用于大多数页面,但也有一些例外情形。
1.3.5 确定输入目的
1.3.5 确定输入目的
- 我们不提供有关自动填充输入字段的自动完成信息。
指导原则 1.4 可识别
指导原则 1.4 可识别
1.4.3 对比度(最低)
1.4.3 对比度(最低)
- 一些文本和文本图像的视觉呈现不具有至少4.5:1的对比度。
1.4.5: 文本图像
1.4.5: 文本图像
- 某些页面中使用一些文本图像
1.4.11 非文本对比度
1.4.11 非文本对比度
- 某些元素与相邻颜色的颜色对比度不是3:1。
指导原则 2.1 可访问键盘
指导原则 2.1 可访问键盘
2.1.1 键盘
2.1.1 键盘
- 无法通过键盘访问Cookie同意的内部链接(第三方组件)
- CAPTCHA位于用于创建Polestar ID(第三方供应商)的表单中,为用户提供了一种联系Polestar支持部门的替代方法。
- 整个网站中有一些模态页面没有键盘陷阱。它允许用户与模式之外的元素进行交互。
指导原则 2.2 计时可调
指导原则 2.2 计时可调
2.2.2 暂停、停止、隐藏
2.2.2 暂停、停止、隐藏
- 一些自动播放和循环播放的视频不提供用于播放或暂停的控件。
指导原则 2.4 可导航
指导原则 2.4 可导航
2.4.1 绕过拦截
2.4.1 绕过拦截
- 我们没有用于绕过多个网页上重复内容拦截的机制。
2.4.3 焦点顺序
2.4.3 焦点顺序
- 有些页面需要进行这方面的改进。
2.4.4 链接用途(上下文中)
2.4.4 链接用途(上下文中)
- 某些链接的用途无法仅通过链接文本或链接文本及其编程确定的链接上下文确定。
指导原则 2.5 输出模态
指导原则 2.5 输出模态
2.5.3 名称中的标签
2.5.3 名称中的标签
- 某些情况下,缺少替代文本。
指导原则 3.3 输入协助
指导原则 3.3 输入协助
3.2.3: 一致的导航
3.2.3: 一致的导航
- 导航抽屉跨不同的子域更改链接。
3.3.1 错误识别
3.3.1 错误识别
- 表单提交后的用户错误通知需要加以改进。
指导原则 5. 合规性
指导原则 5. 合规性
5.2.5 无干扰
5.2.5 无干扰
- 无法通过键盘访问Cookie同意的内部链接(第三方组件)
Polestar strives to ensure digital accessibility for everyone.
Polestar strives to ensure digital accessibility for everyone.
We invest considerable efforts and use the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as a guide to ensure that persons with disabilities will be able to use and enjoy this website in an independent and equal manner.
We invest considerable efforts and use the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as a guide to ensure that persons with disabilities will be able to use and enjoy this website in an independent and equal manner.
We realise though that all areas of our websites are not yet fully accessible, but we are improving our websites’ accessibility features.
We realise though that all areas of our websites are not yet fully accessible, but we are improving our websites’ accessibility features.
This Accessibility Statement provides our current Accessibility status, and we will update this Statement as our compliance efforts continue.
This Accessibility Statement provides our current Accessibility status, and we will update this Statement as our compliance efforts continue.
What we have done
We regularly audit our website to find issues and improve its accessibility. We have worked with an external auditor and focused on solving the most critical issues first. We strive to follow the guidelines of WCAG 2.1, which are perceivable, operable, understandable, and robust, in everything we do, and our ambition is to, as fully as possible, comply with the WCAG 2.1 level AA.
We regularly audit our website to find issues and improve its accessibility. We have worked with an external auditor and focused on solving the most critical issues first. We strive to follow the guidelines of WCAG 2.1, which are perceivable, operable, understandable, and robust, in everything we do, and our ambition is to, as fully as possible, comply with the WCAG 2.1 level AA.
Some of our recent accessibility improvements are:
Some of our recent accessibility improvements are:
- Technical possibility to have alternative texts for images
- Updates in the Heading structure so that the headers are clearly and correctly marked.
- Clear indications of the visible focus on the website
- Improvements in the tab order
- The possibility to pause auto-play videos
- Technical possibility to have Aria labels on controls
- Error messages in form pages
- Landmarks in, for example, the footer
How we are working with accessibility
Our goal is to have a website that is accessible to everyone. To achieve this, we run continuous testing in the course of the development and perform manual audits several times per year. For automated testing, we use HTML validators, browser, and editor plugins.
Our goal is to have a website that is accessible to everyone. To achieve this, we run continuous testing in the course of the development and perform manual audits several times per year. For automated testing, we use HTML validators, browser, and editor plugins.
We support the two latest major versions of the browsers Firefox, Microsoft Edge, Safari, and Chrome.
We support the two latest major versions of the browsers Firefox, Microsoft Edge, Safari, and Chrome.
Despite this, we are aware that we may, at any given time, not pass all available online validation tools. Please find below our strategy for how we aim to improve our customer experience, but also a list of all currently known issues that remain for us to address. We expect these issues to be resolved in future updates of the website redesigns, as they are part of our development backlog.
Despite this, we are aware that we may, at any given time, not pass all available online validation tools. Please find below our strategy for how we aim to improve our customer experience, but also a list of all currently known issues that remain for us to address. We expect these issues to be resolved in future updates of the website redesigns, as they are part of our development backlog.
How we continuously improve
We continuously identify and document any accessibility issues that we find on our website and prioritise them according to the overall impact they have for our visitors, but also based on the level of effort that is required to address them. Issues that greatly affect the website experience from an accessibility perspective are immediately addressed. We take reasonable measures to fix other issues within 6 months from the time of our last audit.
We continuously identify and document any accessibility issues that we find on our website and prioritise them according to the overall impact they have for our visitors, but also based on the level of effort that is required to address them. Issues that greatly affect the website experience from an accessibility perspective are immediately addressed. We take reasonable measures to fix other issues within 6 months from the time of our last audit.
If you encounter any accessibility issues while navigating our digital properties, please contact Polestar support at accessibility@polestar.cn.
If you encounter any accessibility issues while navigating our digital properties, please contact Polestar support at accessibility@polestar.cn.
Be assured that we take your feedback seriously and will consider it as we evaluate ways to accommodate all of our customers.
Be assured that we take your feedback seriously and will consider it as we evaluate ways to accommodate all of our customers.
For information about our processing of your personal data, please read our Privacy notice.
For information about our processing of your personal data, please read our Privacy notice.
Our goal is to comply with the WCAG 2.1 level AA to the greatest extent possible. Below we have documented the guidelines that still are work in progress.
Our goal is to comply with the WCAG 2.1 level AA to the greatest extent possible. Below we have documented the guidelines that still are work in progress.
Guideline 1.1 Text Alternatives
1.1.1 Non-text Content
Guideline 1.1 Text Alternatives
1.1.1 Non-text Content
- Alternative texts are not provided on all pages.
- Alterative texts are mostly provided in English and not local language.
Guideline 1.2 Time-based Media
Guideline 1.2 Time-based Media
- Subtitles / alternative texts are missing on certain videos.
- Certain videos lack the information that they are a decorative video.
Guideline 1.3 Adaptable
1.3.1 Info and Relationships
Guideline 1.3 Adaptable
1.3.1 Info and Relationships
- Some pages do not have a clear heading structure.
- Some unnecessary use of aria.
1.3.2 Meaningful Sequence
1.3.2 Meaningful Sequence
- This is applied to most pages but there are some few exceptions.
1.3.5 Identify Input Purpose
1.3.5 Identify Input Purpose
- We don’t provide autocomplete information about auto-filled input fields.
Guideline 1.4 Distinguishable
Guideline 1.4 Distinguishable
1.4.3 Contrast (Minimum)
1.4.3 Contrast (Minimum)
- Some visual presentation of text and images of text does not have a contrast ratio of at least 4.5:1.
1.4.5: Images of Text
1.4.5: Images of Text
- Some images of text are being used on some pages
1.4.11 Non-text Contrast
1.4.11 Non-text Contrast
- Some elements do not have the color contrast of 3:1 against adjacent colors.
Guideline 2.1 Keyboard Accessible
Guideline 2.1 Keyboard Accessible
2.1.1 Keyboard
2.1.1 Keyboard
- The internal links of the Cookie consent is not accessible via keyboard (3rd party component)
- CAPTCHA is present in the form for creating a Polestar ID (3rd party vendor) but an alternative to contact Polestar support is given to the user.
- There are some modal pages throughout the website that do not have a keyboard trap. It allows users to interact with elements that are outside of the modal.
Guideline 2.2 Enough Time
Guideline 2.2 Enough Time
2.2.2 Pause, Stop, Hide
2.2.2 Pause, Stop, Hide
- Some videos that are auto-play and looping, do not provide controls to play or pause.
Guideline 2.4 Navigable
Guideline 2.4 Navigable
2.4.1 Bypass Blocks
2.4.1 Bypass Blocks
- We don't have a mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
2.4.3 Focus Order
2.4.3 Focus Order
- Some pages need improvement in this area.
2.4.4 Link Purpose (In Context)
2.4.4 Link Purpose (In Context)
- The purpose of some links can’t be determined from the link text alone or from the link text together with its programmatically determined link context.
Guideline 2.5 Input Modalities
Guideline 2.5 Input Modalities
2.5.3 Label in Name
2.5.3 Label in Name
- Alt texts are missing in some cases.
Guideline 3.3 Input Assistance
Guideline 3.3 Input Assistance
3.2.3: Consistent Navigation
3.2.3: Consistent Navigation
- Navigation drawer changes links cross different sub domains.
3.3.1 Error Identification
3.3.1 Error Identification
- Improvements are needed in the error notification for users after form submission.
Guideline 5. Conformance
Guideline 5. Conformance
5.2.5 Non-Interference
5.2.5 Non-Interference
- The internal links of the Cookie consent is not accessible via keyboard (3rd party component)