You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>In relation to <strong>quality assurance</strong>, make sure you:</p>
198
198
<ul>
199
199
<li>Have <ahref="https://w3c.github.io/sustainableweb-wsg/#enable-others-to-understand-and-reuse-your-deliverables">open working and documentation processes</a> such as <ahref="https://w3c.github.io/sustainableweb-wsg/#use-a-design-system-to-prioritize-interface-consistency">design systems</a>.</li>
200
-
<li>Conduct <ahref="https://w3c.github.io/sustainableweb-wsg/#audit-and-test-for-bugs-or-issues-that-require-resolving">regular audits and testing</a>, including <ahref="https://w3c.github.io/sustainableweb-wsg/#ensure-features-provide-maximum-value-for-their-impact">value</a>, <ahref="https://w3c.github.io/sustainableweb-wsg/#verify-that-real-world-users-can-successfully-use-your-work">usability</a>, and <ahref="https://w3c.github.io/sustainableweb-wsg/#check-for-compatibility-or-platform-specific-issues">compatibility</a> testing into releases, as well as using inputs from visitor <ahref="https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance-and-speed">journey tracking</a> to identify issues / opportunities.</li>
200
+
<li>Conduct <ahref="https://w3c.github.io/sustainableweb-wsg/#audit-and-test-for-bugs-or-issues-that-require-resolving">regular audits and testing</a>, including <ahref="https://w3c.github.io/sustainableweb-wsg/#ensure-features-provide-maximum-value-for-their-impact">value</a>, <ahref="https://w3c.github.io/sustainableweb-wsg/#verify-that-real-world-users-can-successfully-use-your-work">usability</a>, and <ahref="https://w3c.github.io/sustainableweb-wsg/#check-for-compatibility-or-platform-specific-issues">compatibility</a> testing into releases, as well as using inputs from visitor <ahref="https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance">journey tracking</a> to identify issues / opportunities.</li>
<p>The performance of a website or application, to identify and resolve bottlenecks or issues in the underlying code or infrastructure which could ultimately impact the sustainability of a website or application, are regularly measured with each release-cycle (using tooling or through research and auditing).</p>
<summaryid="UX26-1">UX26-1: Establish Performance Testing Routines With Each New Release</summary>
1980
1980
<divclass="note" title="About This Technique">
1981
1981
<p><strong>Applicability</strong></p>
1982
-
<p>This technique is <strong>Advisory</strong> to meet <em>Success Criteria</em> within <ahref="https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance-and-speed">2.26 Measure and test for performance and speed</a>.</p>
1982
+
<p>This technique is <strong>Advisory</strong> to meet <em>Success Criteria</em> within <ahref="https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance">2.26 Measure and test for performance</a>.</p>
1983
1983
<p><strong>Description</strong></p>
1984
1984
<p>Encourage a routine to improve web performance within websites and applications due to the established link between web performance optimization and digital sustainability. Running regular benchmarks and working from checklists (either prefabricated or built from scratch) will encourage a schedule to identify potential bottlenecks.</p>
1985
1985
<p>The content of these testing routines can potentially be further tested through automation however at a bare minimum, this list must be utilized in-house to enact sustainable change. For machine testability, if this list is not publicly visible, internal access will be required to determine whether creation has taken place.</p>
<summaryid="UX26-2">UX26-2: Provide Compliance Checks With Each Release for Relevant Legislation</summary>
2009
2009
<divclass="note" title="About This Technique">
2010
2010
<p><strong>Applicability</strong></p>
2011
-
<p>This technique is <strong>Advisory</strong> to meet <em>Success Criteria</em> within <ahref="https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance-and-speed">2.26 Measure and test for performance and speed</a>.</p>
2011
+
<p>This technique is <strong>Advisory</strong> to meet <em>Success Criteria</em> within <ahref="https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance">2.26 Measure and test for performance</a>.</p>
2012
2012
<p><strong>Description</strong></p>
2013
2013
<p>Provide a mechanism during the development process where businesses and individuals creating Web projects can verify that new work meets compliance targets for individual regulations. This technique is most useful when performed with each major milestone as there is a potential for feature (and compliance) breaking material to occur.</p>
2014
2014
<p>Within the scope of sustainability, this is increasingly important as there are explicit laws surrounding the subject in addition to expanded PPP remits such as accessibility, privacy, etc. In terms of machine testability the mechanics of an implementation may be more difficult than utilizing an automated checker, but wizard software can work through questions to help identify key issues.</p>
"title": "Establish Performance Testing Routines With Each New Release",
1786
-
"applicability": "This technique is **Advisory** to meet *Success Criteria* within [2.26 Measure and test for performance and speed](https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance-and-speed).",
1786
+
"applicability": "This technique is **Advisory** to meet *Success Criteria* within [2.26 Measure and test for performance](https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance).",
1787
1787
"description": [
1788
1788
{
1789
1789
"1": "Encourage a routine to improve web performance within websites and applications due to the established link between web performance optimization and digital sustainability. Running regular benchmarks and working from checklists (either prefabricated or built from scratch) will encourage a schedule to identify potential bottlenecks.",
"title": "Provide Compliance Checks With Each Release for Relevant Legislation",
1817
-
"applicability": "This technique is **Advisory** to meet *Success Criteria* within [2.26 Measure and test for performance and speed](https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance-and-speed).",
1817
+
"applicability": "This technique is **Advisory** to meet *Success Criteria* within [2.26 Measure and test for performance](https://w3c.github.io/sustainableweb-wsg/#measure-and-test-for-performance).",
1818
1818
"description": [
1819
1819
{
1820
1820
"1": "Provide a mechanism during the development process where businesses and individuals creating Web projects can verify that new work meets compliance targets for individual regulations. This technique is most useful when performed with each major milestone as there is a potential for feature (and compliance) breaking material to occur.",
0 commit comments