Test Accessibility with Browser Tools

This part of the Web Development path moves from knowing that Accessibility with Browser Tools exists to being able to use it deliberately. By the end, you should be able to explain the mechanism, build or configure a small example, verify the result, and diagnose the most common ways it fails.

In this lesson

• Place Accessibility with Browser Tools in the context of the Accessibility and UX module rather than treating it as an isolated feature.
• Build a mental model for what happens before, during, and after the operation.
• Work through a reproducible example connected to the scenario: build and harden a small documentation-style website with forms and client/server behavior.
• Inspect the result and distinguish evidence from assumption.
• Recognize failure modes, misleading shortcuts, and production constraints.
• Leave with a verification checklist and a practical exercise rather than a memorized snippet.

Read the diagnostic evidence

For a web developer, Accessibility with Browser Tools becomes useful when it changes a decision you can verify. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about Accessibility with Browser Tools: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

The practical question behind test accessibility with browser tools is not simply whether the feature exists, but what behavior it gives you control over. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

Separate symptoms from causes

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Accessibility with Browser Tools. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. In this lesson's Accessibility with Browser Tools example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Accessibility and UX exercise changes the conditions. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Accessibility with Browser Tools over another. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism.

Questions to answer about Accessibility with Browser Tools

1. What is the smallest input or state that makes Accessibility with Browser Tools observable?
2. What does success look like, and how can you prove it without relying on a vague UI message?
3. Which configuration, permissions, types, versions or environment details can change the result?
4. Which failure is most likely for a beginner, and what evidence distinguishes it from a different failure?
5. What should remain true after the example is repeated, automated or moved to another environment?

Build a minimal failing case

In the Accessibility and UX part of this learning path, Accessibility with Browser Tools is deliberately introduced now because later lessons depend on the boundary it establishes. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Accessibility with Browser Tools to the surrounding runtime and operational context. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work.

Fix one variable at a time

For a web developer, Accessibility with Browser Tools becomes useful when it changes a decision you can verify. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

The practical question behind test accessibility with browser tools is not simply whether the feature exists, but what behavior it gives you control over. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work.

Evidence table

What you inspect	What it tells you	What it does not prove
Source/configuration for Accessibility with Browser Tools	What you asked the platform/runtime to do	That the request actually succeeded
Build/validation output	Whether static checks accepted the artifact	That production data and permissions behave correctly
Runtime/result output	What happened for this input	That every edge case is safe
Logs/diagnostics	Where the system spent time or failed	The root cause without interpretation
Repeat test	Whether behavior is reproducible	That the design is optimal

Verify the correction

For this part of Test Accessibility with Browser Tools, move beyond the earlier mental model and ask how the behavior survives repetition. Run or reproduce the step twice, change the ordering or boundary case where safe, and verify that the same invariant still holds. A reliable Accessibility and UX workflow is one that produces evidence you can compare, not one that succeeds only when the exact tutorial sequence is copied.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Accessibility with Browser Tools over another. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. In this lesson's Accessibility with Browser Tools example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Accessibility and UX exercise changes the conditions. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

Positive and negative tests

In the Accessibility and UX part of this learning path, Accessibility with Browser Tools is deliberately introduced now because later lessons depend on the boundary it establishes. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Accessibility with Browser Tools to the surrounding runtime and operational context. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. The specific test here is about Accessibility with Browser Tools: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

Worked example: Accessibility with Browser Tools

The following html example is written specifically for this lesson. Read the requirement first, then predict the important result before running or reproducing it.

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Order status</title>
  <style>
    .status { padding: 1rem; border: 1px solid #bbb; border-radius: .5rem; }
  </style>
</head>
<body>
  <main>
    <h1>Order status</h1>
    <p class="status" id="status">Ready</p>
    <button id="refresh" type="button">Refresh</button>
  </main>
  <script>
    document.querySelector('#refresh').addEventListener('click', () => {
      document.querySelector('#status').textContent = 'Updated just now';
    });
  </script>
</body>
</html>

Expected observation

A page with a Refresh button; clicking it changes the status text.

Read the example deliberately

• Line/construct 1: <!doctype html> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 2: <html lang="en"> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 3: <head> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 4: <meta charset="utf-8"> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 5: <meta name="viewport" content="width=device-width, initial-scale=1"> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 6: <title>Order status</title> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 7: <style> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 8: .status { padding: 1rem; border: 1px solid #bbb; border-radius: .5rem; } — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 9: </style> — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 10: </head> — identify what state or contract this introduces, then trace where that state is consumed.

Do not stop at “it ran.” Change one meaningful value related to Accessibility with Browser Tools, predict the new result, run/reproduce the example again, and explain why the output changed. That mutation test is a stronger check of understanding than copying the original result.

Automation and repeatability

Now apply Accessibility with Browser Tools to the current Automation and repeatability concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Web Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

The practical question behind test accessibility with browser tools is not simply whether the feature exists, but what behavior it gives you control over. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. In this lesson's Accessibility with Browser Tools example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Accessibility and UX exercise changes the conditions.

Logging and diagnostics that help later

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Accessibility with Browser Tools. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work.

Now apply Accessibility with Browser Tools to the current Logging and diagnostics that help later concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Web Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Failure-mode matrix

Symptom	Likely category	First evidence to collect
The Accessibility with Browser Tools behavior never occurs	configuration / control flow	verify the relevant code/configuration is actually reached
Build or validation fails	syntax / type / unsupported option	read the first meaningful diagnostic, not the last cascade message
Works locally but not elsewhere	environment / version / permission	compare runtime versions, identity, configuration and data
Result is valid but wrong	assumption / data shape / business rule	inspect intermediate values and boundary conditions
Intermittent behavior	concurrency / timing / external dependency	add timestamps, correlation IDs or deterministic reproduction

Common false leads

In the Accessibility and UX part of this learning path, Accessibility with Browser Tools is deliberately introduced now because later lessons depend on the boundary it establishes. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about Accessibility with Browser Tools: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Accessibility with Browser Tools to the surrounding runtime and operational context. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism. In Web Development lesson 29 — Test Accessibility with Browser Tools, use that observation as the checkpoint for this exact Accessibility and UX topic rather than generalizing it beyond the evidence.

Prevent the same failure from returning

For a web developer, Accessibility with Browser Tools becomes useful when it changes a decision you can verify. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. In this lesson's Accessibility with Browser Tools example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Accessibility and UX exercise changes the conditions.

For the Prevent the same failure from returning part of Test Accessibility with Browser Tools, use a separate verification pass rather than repeating the earlier explanation. Focus on Accessibility with Browser Tools under one changed condition and write down the before/after evidence. This is verification pass 2 for Web Development lesson 29: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Accessibility and UX workflow.

Production incident perspective

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Accessibility with Browser Tools. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Accessibility with Browser Tools over another. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work.

Troubleshooting checklist

Now apply Accessibility with Browser Tools to the current Troubleshooting checklist concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Web Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Accessibility with Browser Tools to the surrounding runtime and operational context. At the intermediate stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. In this lesson's Accessibility with Browser Tools example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Accessibility and UX exercise changes the conditions.

What can fail in Accessibility with Browser Tools

For the What can fail in Accessibility with Browser Tools part of Test Accessibility with Browser Tools, use a separate verification pass rather than repeating the earlier explanation. Focus on Accessibility with Browser Tools under one changed condition and write down the before/after evidence. This is verification pass 3 for Web Development lesson 29: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Accessibility and UX workflow.

In What can fail in Accessibility with Browser Tools, look at Accessibility with Browser Tools through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Web Development, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Accessibility and UX module should be based on what you measured rather than on a repeated rule of thumb.

Make the failure reproducible

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Accessibility with Browser Tools. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about Accessibility with Browser Tools: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

For the Make the failure reproducible part of Test Accessibility with Browser Tools, use a separate verification pass rather than repeating the earlier explanation. Focus on Accessibility with Browser Tools under one changed condition and write down the before/after evidence. This is verification pass 4 for Web Development lesson 29: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Accessibility and UX workflow.

Observe before changing anything

This section needs a different question from the earlier explanation: what would make Accessibility with Browser Tools fail specifically while working through Observe before changing anything? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Test Accessibility with Browser Tools is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

For the Observe before changing anything part of Test Accessibility with Browser Tools, use a separate verification pass rather than repeating the earlier explanation. Focus on Accessibility with Browser Tools under one changed condition and write down the before/after evidence. This is verification pass 5 for Web Development lesson 29: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Accessibility and UX workflow.

A production-oriented walkthrough for Accessibility with Browser Tools

1. Establish the Accessibility with Browser Tools behavior

2. Inspect the Accessibility with Browser Tools behavior

3. Implement the Accessibility with Browser Tools behavior

A useful variation is to introduce one boundary case that is plausible for Accessibility with Browser Tools: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. In this lesson's Accessibility with Browser Tools example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Accessibility and UX exercise changes the conditions.

4. Exercise the Accessibility with Browser Tools behavior

5. Challenge the Accessibility with Browser Tools behavior

A useful variation is to introduce one boundary case that is plausible for Accessibility with Browser Tools: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work.

6. Verify the Accessibility with Browser Tools behavior

7. Harden the Accessibility with Browser Tools behavior

Harden this step in the context of build and harden a small documentation-style website with forms and client/server behavior. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a browser, DevTools, editor and local development server. For Accessibility with Browser Tools, apply this check in the context of the Accessibility and UX workflow before carrying the assumption into later Web Development work.

A useful variation is to introduce one boundary case that is plausible for Accessibility with Browser Tools: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. Keep this point tied to Accessibility with Browser Tools. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Accessibility and UX lesson are specific to this mechanism.

8. Document the Accessibility with Browser Tools behavior

Failure patterns worth recognizing early

Treating Accessibility with Browser Tools as syntax instead of behavior

If you can reproduce the syntax but cannot predict the state after it runs, the lesson is not finished. Rewrite the example in your own words and name the input, operation and observable result.

Copying a configuration from a different version

Web Development tooling evolves. Compare the documentation version, runtime/tool version and project settings before assuming that a screenshot or command from another environment applies unchanged.

Verifying only the happy path

A successful first run proves one path. Add at least one negative or boundary case relevant to Accessibility with Browser Tools. The failure should be intentional and the diagnostic should make sense.

Hiding the important state behind too much abstraction

Abstraction is useful after the behavior is understood. During the first implementation of Accessibility with Browser Tools, keep the decisive state and control flow visible enough to debug.

Diagnosing Accessibility with Browser Tools systematically

Use this order when Accessibility with Browser Tools does not behave as expected:

1. Reproduce the smallest failing case.
2. Confirm the actual version/toolchain/environment.
3. Capture the first meaningful diagnostic or unexpected value.
4. Verify identity, permissions and configuration if the operation crosses a service boundary.
5. Inspect intermediate state rather than only the final UI.
6. Change one variable and rerun.
7. Compare the corrected behavior with a negative case.
8. Record the final cause so the same failure is faster to diagnose next time.

Put Accessibility with Browser Tools under pressure

Extend the worked scenario so that Accessibility with Browser Tools must handle one additional real constraint. Choose one: a second data shape, a failed dependency, an invalid input, a permission difference, a repeat operation, or a larger workload. Before implementing the change, write down the behavior you expect and the evidence that will prove it.

Your result is complete when another learner can reproduce the change from your notes, observe the expected behavior, and intentionally trigger at least one documented failure without damaging their environment. The specific test here is about Accessibility with Browser Tools: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

Can you explain and verify Accessibility with Browser Tools?

• Can you define Accessibility with Browser Tools without using the exact wording of an API/reference page?
• Can you identify the boundary where Accessibility with Browser Tools begins and where another concept takes over?
• Can you predict the result of the worked example before running it?
• Can you explain one failure from evidence rather than guessing?
• Can you name one production constraint that the beginner example intentionally simplifies?
• Can you repeat the example from a clean state?

The durable ideas from Accessibility with Browser Tools

• Accessibility with Browser Tools is useful because it controls observable behavior, not because it adds another piece of syntax to memorize.
• Verification belongs in the workflow: build/check, run/reproduce, inspect, challenge, and repeat.
• The Accessibility and UX module uses this lesson as a foundation for the next decisions in the Web Development learning path.
• Official documentation is the source of truth for version-specific contracts; tutorials should teach you how to read and apply those contracts.

Source material for version-specific details

The following primary documentation was used as a factual reference map for this lesson. ScrutnLearn's explanation is original synthesis rather than copied documentation prose.

• MDN accessibility
• MDN CSS
• MDN HTML
• MDN Learn Web Development
• React Learn