98-383 Introduction to Programming Using HTML and CSS Exam Guide
Exam 98-383, Introduction to Programming Using HTML and CSS, validates foundational ability to recognize and write syntactically correct HTML and CSS, structure webpage content, and create and apply styles. It is aimed at beginners, students, and candidates building an entry-level foundation in web development rather than demonstrating advanced application programming. This guide helps you make the practical decision that matters first: whether to prepare for this specific HTML5 and CSS3 objective set, or verify current availability before investing further study time.
What does exam 98-383 validate?
The exam focuses on the core construction of a webpage: well-formed HTML, meaningful document structure, navigation, forms, multimedia, CSS syntax, selectors, stylesheets, and precedence. The published exam design expects candidates to recognize and write syntactically correct HTML and CSS, structure data with HTML elements, and create and apply CSS styles.
The technology area is HTML and CSS, and the published language version is HTML5 and CSS3. The exam is identified in the official document as an MTA credit-type exam. That combination makes the objective set a foundation-level checkpoint: it tests whether you understand the building blocks and can use them correctly, not whether you can design a complete production system.
Who should consider it?
This exam is most relevant to a beginner who needs a structured target for learning webpage markup and styling. It can also suit a student, educator, or early-career candidate who wants an external measure of basic HTML and CSS knowledge before moving to broader web-development work.
Do not choose it solely because you already use a visual page builder or can copy a template. The objectives require understanding what elements, attributes, selectors, stylesheets, and links do. If your experience is limited to changing text and colors through a graphical interface, plan for hands-on coding rather than relying on familiarity with finished pages.
What it does not establish
The supplied objectives describe HTML and CSS skills. They do not establish advanced JavaScript, server-side programming, database development, framework expertise, or professional front-end engineering ability. Treat the exam as a baseline credential or study milestone, not as evidence that you can independently deliver every part of a modern web application.
Microsoft Learn’s beginner path similarly frames HTML and CSS as introductory webpage-building skills and includes a separate module on accessibility. That learning path can support preparation, but completing it should not be treated as proof that every exam objective has been mastered.
Which skills appear in the published objectives?
Use the objective document as your checklist, then prove each topic by writing or correcting code. The published skills cover HTML fundamentals and document structure, navigation, forms, multimedia, and CSS fundamentals. A useful preparation plan gives each area both a knowledge review and a small implementation task.
No blueprint percentages are supplied in the verified facts for this guide. Do not create a study schedule from unattributed percentage charts or compare bare percentages from third-party pages. Work from the named domains and give extra time to any area where you cannot explain the result of your code.
HTML fundamentals and document structure
The objectives include metadata elements and well-formed markup. They also include headings, paragraphs, divisions, spans, lists, and tables. Your practice should cover the purpose and nesting of these elements, correct opening and closing syntax where applicable, meaningful document organization, and the difference between a structural element and an inline span.
HTML5 semantic elements are specifically included: header, nav, section, article, aside, footer, details, summary, figure, and caption. Practice choosing an element because of the role it plays in the document, not merely because it produces a familiar visual appearance. For example, a navigation region should be represented as navigation rather than as an arbitrary container whose only purpose is styling.
A strong exercise is to create a small article page containing a document header, navigation, a main section, an article, an aside, a figure with a caption, and a footer. Inspect the nesting and then deliberately introduce one markup error. The goal is to learn how to identify the error and explain why the corrected structure is preferable.
Navigation and links
The published skills include navigation with image links, anchors, targets, bookmarks, and relative or absolute links. Prepare to distinguish a link’s destination from the text or image that activates it, and to reason about how a path changes when the linked file is in another directory.
Build a two-page practice site with a navigation list, an image used as a link, a link to a location on the same page, and links between files in separate folders. Add a target or bookmark, test every destination, and then move one file so that you must repair a relative path. This reveals whether you understand path resolution rather than simply remembering a single syntax pattern.
A common mistake is treating every broken link as an HTML problem. The markup may be valid while the relative path is wrong. Check the current document’s location, the destination’s location, spelling, and whether the link is intended to leave the site or move within it.
Forms and controls
The form objectives include action and method attributes, input types, select, textarea, button, output, option, datalist, and fieldset. Study the role of each control and the relationship between a form, its controls, and the destination specified by the form attributes.
Create a registration or feedback form without depending on a framework. Include grouped controls, a selection list, a multiline text field, a button, an output area, and a datalist. For each control, write down what data it represents and how its HTML communicates that purpose. Then review whether the structure remains understandable when visual styling is removed.
Do not confuse a control’s appearance with its semantic type. A text input styled to look like another control does not automatically provide the same meaning or behavior. Similarly, knowing an attribute name is not enough; you should be able to read a short form and identify what its action and method are intended to do.
Multimedia elements
The published multimedia skills include img, picture, SVG, canvas, video, audio, track, source, and simple iframe implementations. Study the purpose of each element and the way source or supporting elements relate to the primary media element.
Use a practice page that contains an image, a picture element, a simple SVG, a canvas example, video and audio elements, a track, source entries, and a simple iframe. The exercise does not need to be elaborate. The important result is that you can identify the element being used, the content it presents, and the reason a supporting element appears inside it.
A frequent preparation error is learning multimedia through browser defaults alone. Default controls and appearance can vary, so inspect the markup and explain the structure independently of how the browser happens to render it. Keep the exercise focused on the published element set rather than adding unrelated media APIs.
CSS fundamentals
The CSS objectives include inline, internal, and external stylesheets, precedence, selectors, and rule-set syntax. You should be able to recognize a valid rule, identify the selector and declarations, explain where a style is defined, and reason about which competing rule is applied.
Make one page that uses all three stylesheet approaches, then apply competing declarations to the same element. Record which declaration takes effect and why. Change one selector at a time and observe the result. This is more useful than memorizing isolated definitions because it forces you to connect source location, selector matching, and precedence.
Study rule-set syntax carefully. A missing brace, misplaced colon, incorrect selector, or malformed declaration can change how the browser interprets the stylesheet. When debugging, isolate the smallest rule that demonstrates the issue, validate the syntax, and then add complexity back gradually.
How should you prepare if you are starting from zero?
Start with a working page, not a glossary. Write a minimal HTML document, add meaningful content, connect a stylesheet, and view the result in a browser. Then expand the same page through the objective areas. This sequence lets each new topic attach to a visible structure while exposing syntax and nesting errors early.
The official preparation guidance expects approximately 100 hours of HTML and CSS instruction and/or hands-on experience. That figure is a planning reference, not a guarantee that every candidate needs exactly the same amount of time. Use an initial diagnostic to decide whether you need broad instruction, targeted repair, or mostly objective-based revision.
Phase one: establish markup control
Begin with document metadata, well-formed markup, headings, paragraphs, divisions, spans, lists, and tables. For every exercise, type the markup yourself and check whether you can describe the document tree in plain language. If you cannot explain why an element is nested inside another, pause and repair that understanding before adding CSS.
Keep a short error log. Record the original code, the observed problem, the correction, and the rule that explains the correction. Typical entries might involve an unclosed element, incorrect nesting, a link path, or a selector that matches more or fewer elements than intended. Review the log at the end of each study session.
Phase two: add semantics, navigation, and forms
Once basic structure is reliable, rebuild the page with the named HTML5 semantic elements. Add internal bookmarks and links between files, then create a form containing the published controls. Keep styles modest at this stage so that you can see whether the HTML itself is correct.
Use a deliberate test matrix: one row for each link destination, form control, and semantic region; one column for expected behavior; and one column for the result. This prevents a visually attractive page from hiding untested objectives. It also gives you a concrete list of corrections for the next session.
Phase three: add multimedia and CSS reasoning
Next, add the published multimedia elements and move styling from inline declarations to an internal or external stylesheet. Introduce selectors and competing rules in small steps. After each change, predict the result before refreshing the page, then compare the prediction with the browser output.
At this stage, avoid spending most of your time on visual polish. Color palettes, animations, elaborate layouts, and framework conventions are less useful than being able to read a short stylesheet, identify a matching selector, and explain why one rule takes precedence over another.
Phase four: work from the objective list
Finish by converting every published skill into a demonstration task. “Understand forms” is too vague to assess; “create a form using action, method, select, textarea, button, output, option, datalist, and fieldset, then explain each part” is observable. Mark a topic ready only when you can complete it without copying a solution.
Mix topics in later practice. A final page might combine semantic structure, a relative link, an internal bookmark, a form, a media element, and an external stylesheet. Mixed exercises expose context-switching problems that isolated drills can conceal, while still keeping the work inside the published scope.
What should a practical study roadmap look like?
A useful roadmap moves from syntax to structure, then from isolated features to mixed implementation. Allocate the official approximately 100-hour preparation reference according to your diagnostic rather than splitting time evenly by assumption. Every study block should end with working code, a correction, or a written explanation of a behavior you tested.
If you have less experience, spend the early part of the plan learning and building together. If you already create simple pages, shorten the introductory review and use the saved time for objective-by-objective diagnostics, link paths, form structure, multimedia markup, and CSS precedence.
A four-stage schedule
Stage one is foundation work. Learn and practice metadata, well-formed markup, common content elements, lists, tables, and basic CSS rule-set syntax. Your checkpoint is a small page that remains understandable when viewed as source rather than only as a rendered screen.
Stage two is structural expansion. Add semantic HTML5 elements, navigation with relative and absolute links, anchors, targets, and bookmarks. Test the page after changing its folder arrangement so that you must reason about relative paths.
Stage three is interaction and presentation. Build the form controls named in the objectives, add multimedia elements, and apply inline, internal, and external stylesheets. Test competing selectors and document your explanation of precedence rather than accepting the first visual result.
Stage four is verification. Use a fresh, mixed exercise and a closed-notes objective review. For each missed task, identify whether the weakness is vocabulary, syntax, element choice, path resolution, selector matching, or precedence. Repair the underlying category, then repeat the task in a new example.
How to use Microsoft Learn productively
Microsoft Learn provides a beginner learning path titled “Build web pages with HTML and CSS for beginners.” Its listed modules cover building a first HTML webpage, using CSS styles in a webpage, and learning the basics of web accessibility. It is a sensible starting resource for candidates who need guided instruction and a browser-based coding workflow.
Use the path as a foundation, then cross-reference the official 98-383 objectives. The learning path’s scope and organization do not replace the exam objective document. Make a separate checklist for links, form controls, multimedia, metadata, semantic elements, and CSS precedence so that a completed learning path does not create a false sense of coverage.
Which mistakes waste the most preparation time?
The most expensive mistakes are usually process mistakes: studying only definitions, copying complete pages, ignoring broken links, polishing appearance before checking structure, and trusting unofficial question collections as a substitute for skill. Replace passive review with short implementation tasks and explanations that show what the code is doing.
A candidate who can reproduce a snippet but cannot modify it is not yet ready for reliable objective-based practice. Change one requirement at a time, predict the result, test it, and record the reason for the correction. That routine builds transferable understanding without depending on live or leaked exam content.
Mistake: treating rendered appearance as proof
A page can look acceptable while its markup is poorly structured or its stylesheet contains fragile rules. Review the source, inspect nesting, and test the page after removing or changing styles. The published objectives concern recognizing and writing HTML and CSS, so source-level reasoning deserves as much attention as the visible result.
Mistake: memorizing element names without purpose
A long list of tags is not a working mental model. For each published element, connect its name to its role, expected location, attributes or supporting elements, and a small use case. Then practice selecting the appropriate element when given a page requirement rather than being told which tag to type.
Mistake: ignoring CSS conflicts
Applying one successful style does not demonstrate understanding of precedence. Create controlled conflicts between inline, internal, and external stylesheets and between selectors. Explain the outcome before changing the code. If your explanation is uncertain, simplify the example until the source of the result is clear.
Mistake: relying on dumps or recalled questions
Question dumps and alleged exam recalls are not a dependable way to establish the published HTML and CSS skills. They may be inaccurate, outdated, or outside the objective set, and memorization does not guarantee passing. Use legitimate objective documents, instruction, and original coding exercises instead.
How can you tell whether you are ready?
Readiness is demonstrated by independent performance across the objective areas, not by recognizing familiar wording. Start with a blank file and complete a small page that combines structure, navigation, a form, multimedia, and CSS. Then explain each major decision and repair deliberately introduced errors without looking up the answer.
Use three checks before scheduling or attempting the exam. First, coverage: every named skill has a completed exercise. Second, accuracy: your markup and styles work after you retest them. Third, explanation: you can state why an element, link path, selector, or stylesheet rule produces the result you observe.
Build a personal readiness checklist
Your checklist should include metadata and well-formed markup; headings, paragraphs, divisions, spans, lists, and tables; semantic HTML5 elements; image links, anchors, targets, bookmarks, and relative or absolute links; form attributes and controls; multimedia elements; and inline, internal, and external CSS with selectors, rule-set syntax, and precedence.
For each item, use a status such as “can explain,” “can write,” and “can troubleshoot.” A topic should not be marked complete merely because you have read about it. The troubleshooting column is particularly useful because it distinguishes recognition from practical command.
Run a final mixed exercise
Create a simple informational page from a written brief. Include a semantic structure, navigation to another file and to a bookmark, a form with several control types, one or more media implementations, and an external stylesheet. Do not copy a finished template. Afterward, review the source against the objective checklist and correct the weakest area.
Repeat the exercise with a different content theme. Changing the subject forces you to apply the same skills without relying on memorized placement. Keep the task small enough to finish and inspect carefully; the purpose is objective verification, not portfolio design.
What delivery and availability details are supported?
The official objective document identifies VUE and Certiport as exam providers and lists availability in English, Japanese, Traditional Chinese, Simplified Chinese, Spanish, Portuguese-Brazilian, French, German, and Korean. Because provider procedures and exam availability can change, confirm the current registration route, language, and scheduling options directly with the relevant official provider before making plans.
The supplied current Certiport MTA objectives page lists other MTA exams but does not list 98-383 among the exams shown. A Microsoft Q&A post also contains a user statement that the exam was retiring and that vouchers were no longer sold, but that is not enough to establish a current retirement date or universal availability status. Treat availability as a decision to verify, not as an assumption.
Check availability before committing to a long plan
First, consult the current official exam or provider information and confirm that 98-383 can still be scheduled in your region and language. If it is not available, use the published objectives as a foundation for HTML and CSS learning, but do not represent completion of study as a current 98-383 result.
Do not rely on an old page, an archived voucher offer, or a forum statement as the final scheduling authority. The official sources supplied here include historical support discussions and an objectives page whose displayed exam list does not include 98-383. Their presence is useful context, but current registration confirmation must come from the provider.
What if scheduling access fails?
A Microsoft Q&A support response for a scheduling-access problem advises trying Edge, clearing cache and cookies, using an InPrivate session, and returning to the exam page; if the problem persists, it directs the candidate to Pearson VUE Support and the Microsoft Certification Program support forum. These are historical troubleshooting instructions, so verify the current support path before acting on them.
Keep your account details and any scheduling error wording available when contacting support. Avoid repeatedly changing unrelated profile information while troubleshooting. The goal is to isolate a browser or account-access problem and then use the provider’s current support channel if the documented steps do not resolve it.
How should you handle result or certificate questions?
A Microsoft Q&A discussion records a candidate asking about a missing confirmation and certificate after reporting a passed 98-383 attempt. The response directs exam-result questions to certification-profile and score-report support forums. This does not establish a universal result-delivery timeline, so do not plan around an invented number of hours or days.
If a result or certificate is not visible, check the official certification profile or score-report support route and retain your registration and appointment information. Forum discussions can point you toward the right category, but the provider’s current support process is the authoritative next step.
What should you do next?
Make the availability check first, then download or review the official objective document and mark your current ability against each named skill. Begin with one plain HTML page and one external stylesheet, not with exam-question memorization. Within the first study session, identify whether your main gap is markup, document structure, links, forms, multimedia, or CSS reasoning.
If 98-383 is available for your intended route, choose a study cadence that can support repeated hands-on practice and use the approximately 100-hour official preparation reference as a realistic planning anchor. If availability is unclear or unavailable, continue building the same HTML5 and CSS3 foundation while confirming the appropriate current certification or learning alternative through official channels.
Before any attempt, complete a mixed page from a blank file, test every link and control, review the source, and explain the CSS outcome. That final sequence turns the objective list into evidence of ability and gives you a clear basis for deciding whether to schedule, study longer, or redirect your plan.
Conclusion
Exam 98-383 preparation is best treated as a small coding curriculum with a verification point, not as a memorization exercise. Confirm that the exam is currently schedulable, use the official objective list as the boundary of study, and build progressively from well-formed HTML to semantic structure, navigation, forms, multimedia, and CSS precedence. Your next action is simple: verify availability, create the objective checklist, and complete a baseline page so that your study time follows demonstrated gaps rather than guesswork.
