=== Ariade === Contributors: anblik Author: Shivaji Mitra Company: M/S. Anblik Requires at least: 6.6 Tested up to: 7.1 Requires PHP: 7.4 Stable tag: 1.7.134 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Ariade - a WCAG 2.2 AA Full Site Editing (FSE) WordPress block theme for accessible professional-services and business websites. == Description == Live demo: https://showcase.ananyoo.com/ Documentation: https://ananyoo.com/ariade-accessible-wordpress-theme/documentation/ Ariade ships accessible header navigation, predesigned, conformant page patterns, and an accessible footer toolkit: a newsletter band, theme-styled social links (a core Social Icons block turned into brand-magenta discs that match the footer contact icons, keyboard/focus friendly, no icon font) and W3C / accessibility verification badges laid out on one clean line - plus a ready-made "Footer: Connect" pattern that drops the whole Connect column in. The free Ariade Header and Menu plugin adds the theme's simple accessible drop-down menu header (keyboard operable, disclosure pattern, ARIA, Escape-to-close, mobile drawer), and the Ananyoo accessibility plugins add a screen-reader-tested carousel, forms and login. An optional top bar above the header holds "Need help?" links and a short message. When a translation plugin (TranslatePress, Polylang or WPML) or a WooCommerce currency plugin (WPML Multilingual & Multicurrency for WooCommerce, or WooPayments multi-currency) is active, Ariade adds accessible language and currency pickers to the top bar and the footer, in the same style as the Ariade themes for Shopify and BigCommerce. Each picker is a keyboard-operable button that opens a list, the current choice is announced to screen readers, and each language name carries its own lang attribute so it is pronounced correctly. Translation-ready, with a translation template (languages/ariade.pot) and a complete French translation included. Built by M/S. Anblik (https://ananyoo.com). == Accessibility == Ariade targets WCAG 2.2 Level AA and carries the accessibility-ready tag. It is built with semantic HTML, named landmarks (a "Primary" navigation and a "Pagination" navigation), a skip link, keyboard-operable components (header navigation, mobile menu, FAQ accordions), a visible two-tone focus indicator on every control (inverted on dark backgrounds), contrast-checked text and form-field borders, underlined links in content, named pagination links ("Page 2", "Page 3, current page"), screen-reader status messages on the search results and no-results pages, focus management around the comment form (Reply, Cancel reply, after posting), and screen-reader text wherever a visual-only cue is used (ratings, icons, plan buttons). Images used purely for decoration carry an empty alt. The theme does not open links in new windows and does not use autoplaying media or animation beyond reduced-motion-safe transitions. The theme was audited manually against the WordPress accessibility-ready requirements and WCAG 2.2 AA (NVDA, JAWS, keyboard, 200 and 400 percent zoom, text spacing, colour contrast) on a WordPress Theme Unit Test install, and every theme finding was fixed before this version. The Sitemap page is built from core blocks (Page List, Categories and recent posts) with an ordered H1 > H2 heading structure and list semantics. A richer auto-populated Sitemap block is available in the Ariade Header and Menu plugin. Automated tools cover only part of WCAG, so manual keyboard and screen-reader testing (NVDA, JAWS, VoiceOver) on a production install is still recommended. == Installation == 1. Upload the ariade folder to /wp-content/themes/ (or install the .zip via Appearance > Themes > Add New > Upload Theme). 2. Activate through Appearance > Themes. 3. Set a static front page (Settings > Reading > "A static page") to use the Ariade homepage layout, or the front-page template renders it automatically. == Ariade branding switch == Out of the box the theme is neutral: your logo or site title in the header, no theme mark in the hero, and a plain footer with your site title, tagline, page list, latest posts and one small "Theme: Ariade" credit. The showcase look (bundled Ariade logo when no site logo is set, brand mark in the hero, and the footer with the newsletter band and Theme / Plugins / Company columns) is still in the theme for demo sites. To switch it on, add this line to a small plugin or to a child theme's functions.php: add_filter( 'ariade_branding', '__return_true' ); The footer template part renders the pattern ariade/footer, which picks the right footer for the switch. If you have edited the footer in the Site Editor, use "Reset" on the Footer template part so the theme version loads again. == Newsletter setup (Mailchimp, MailerLite, Brevo, etc.) == The footer (branding switch on) ships a visual newsletter band with an email input and Subscribe button. That block is a DESIGN PLACEHOLDER and does not submit anywhere on its own -- themes on wordpress.org are not permitted to integrate with third party services or store subscriber data, so the actual signup is handled by a plugin of your choice. The theme styles the plugin form automatically so it inherits the footer visual (gradient band, white pill input, white pill button). We recommend the free Mailchimp for WordPress plugin (500,000+ installs, GPL, actively maintained). The theme has been tested against its output. The same slot works with MailerLite, Brevo, Constant Contact and Sendinblue plugins in the same way -- any form plugin that outputs a standard shortcode or block can replace the placeholder. Step by step for Mailchimp for WordPress: 1. Install the plugin from Plugins > Add New. Search for "Mailchimp for WordPress" by ibericode. Activate it. 2. In your Mailchimp account, create an API key (Account > Extras > API keys) and copy it. 3. In WordPress, go to Mailchimp for WP > Mailchimp, paste the API key and save. The plugin will list your audiences. 4. Go to Mailchimp for WP > Form. Create a form, pick the audience, adjust the labels if you like. Save. Note the form ID shown on the form list. 5. Go to Appearance > Editor > Template Parts > Footer. Find the newsletter HTML block (the visual placeholder with the Email address label and Subscribe button). Delete that HTML block. In its place add a Shortcode block and paste [mc4wp_form id="XX"] using your form ID. 6. Save the template part. The footer form now submits to Mailchimp with the theme's visual language applied automatically. The theme styles .mc4wp-form inside .site-footer to match the placeholder exactly -- white pill input, white pill submit button, uppercase eyebrow label, response messages coloured to fit the gradient band. If you use a different plugin, add its wrapper class to your child theme with the same rules; the source rules live under the "Mailchimp for WordPress (mc4wp) integration" comment in /assets/css/theme.css. Contact form: the contact page patterns include a similar placeholder slot. We recommend the free Ananyoo Accessible Forms plugin (https://wordpress.org/plugins/ananyoo-accessible-forms/) for a WCAG 2.2 AA form with labels, focus states and announced errors. Drop its shortcode or block in place of the placeholder paragraph the pattern ships with. == Cover images == Recommended size for a blog post cover (featured image): 1600x900 pixels, 16:9. The blog cards (posts loop) and the default single-post header (aurora) both show covers in a 16:9 box, so a 16:9 cover is never cropped anywhere in the theme. Any other shape is centred and trimmed by object-fit: cover, so keep logos, badges, faces and text inside the middle 80 percent of the picture; that also protects the image when social networks crop the preview to 1.91:1 (1200x630). Your SEO plugin can set a separate share image if the cover carries a badge near an edge. To use another ratio site-wide, open Site Editor > Templates > Single Posts, select the Featured Image block and change its Aspect ratio; the editorial (21:9), split and cover single-post layouts keep their own framing. == Fonts == Barlow Semi Condensed and Geist are bundled in /assets/fonts and registered through theme.json (fontFace), so no font is loaded from Google Fonts or any other remote server. Nothing leaves the visitor's browser to fetch a font. == Copyright == Ariade WordPress Theme, Copyright 2026 Shivaji Mitra (M/S. Anblik) Ariade is distributed under the terms of the GNU GPL v2 or later. This theme bundles the third-party resources listed below; every one of them is GPL-compatible. == Images / illustrations == All images in assets/images are original works by the theme author, Shivaji Mitra (M/S. Anblik, https://ananyoo.com), and are released under CC0-1.0 / GPL-2.0-or-later: * Photographic images (hero-*.webp, portrait-*.webp, product-*.webp) were created by the theme author using Adobe Firefly (Adobe's commercially safe image models). * Remaining vector artwork (*.svg) is original flat illustration by the theme author. No third-party or stock photography is bundled in the theme. == Bundled fonts == * Barlow Semi Condensed - Copyright 2017 The Barlow Project Authors (https://github.com/jpt/barlow). Licensed under the SIL Open Font License 1.1 (assets/fonts/OFL-BarlowSemiCondensed.txt). * Geist - Copyright 2023 Vercel, in collaboration with basement.studio. Licensed under the SIL Open Font License 1.1 (assets/fonts/OFL-Geist.txt). * Country flags (assets/flags/*.svg), shown next to currencies in the currency picker - from flag-icons by Panayiotis Lipiridis (https://github.com/lipis/flag-icons). Licensed under the MIT License (assets/flags/LICENSE-flag-icons.txt). * Card artwork (assets/img/card-art/art-1.svg to art-6.svg) - Copyright 2026 Shivaji Mitra, M/S. Anblik. Drawn for this theme and released under GPLv2 or later, the same licence as the theme. == Changelog == = 1.7.134 = * Product pages: the 1px size of the hidden swatch select (1.7.133) is now enforced. WooCommerce's own variation styles are more specific and still gave it a 70% minimum width; the hidden select now stays inside the page on every screen size. = 1.7.133 = * Theme Check: the French translation file languages/fr_FR.l10n.php no longer contains raw control characters (the separator between a context and its text is now written as an escape), so Theme Check no longer warns about non-printable characters. The translations are unchanged. * Product pages: the hidden native select behind the colour and size swatches is now really 1px wide. WooCommerce gives selects a minimum width, which made the hidden select stick out past the right edge of the page on wide screens (it was clipped, so nothing showed, but the page measured wider than the window). = 1.7.132 = * Fix: with TranslatePress, the language picker on a translated page sent visitors back to the same translated page instead of the other language (TranslatePress rewrote every link to the current language). Language links and language names now carry data-no-translation, so the links keep their target and language names always stay in their own language, also with automatic translation switched on. = 1.7.131 = * The "Main features" section of the front page pattern now names the language and currency pickers: the "Multilingual & RTL" card is now "Multilingual & multi-currency" ("Language and currency pickers, French included and right-to-left support, so accessibility travels across languages."). French translation updated to match. = 1.7.130 = * New: the theme now ships a translation template (languages/ariade.pot) for translating Ariade with Poedit, Loco Translate or similar tools, and a complete French translation (languages/fr_FR.po and fr_FR.mo). On a French site, or on the French pages of a site that uses TranslatePress, Polylang or WPML, the theme's buttons, labels, screen-reader text and pattern text now appear in French. * The readme description now explains the top bar and the language and currency pickers, and the "Help & resources" card on the Ariade dashboard (Appearance > Ariade) names the pickers in its Top bar link. = 1.7.129 = * New: language and currency pickers, in the same places and style as the Ariade themes for Shopify and BigCommerce: at the end of the top bar and in the middle of the footer's bottom bar. They appear only when a translation plugin (TranslatePress, Polylang or WPML) or a WooCommerce currency plugin (WPML Multilingual & Multicurrency for WooCommerce, or WooPayments multi-currency) is active, and only when it offers more than one language or currency; without such a plugin nothing changes. Each picker is a button that opens a list (Escape closes it and returns focus to the button). The current choice is marked for screen readers and with a bar on the left. Language names are shown in their own language with the right lang attribute, so screen readers pronounce them correctly. Currencies show their name, code, symbol and a small flag. On phones one button at the end of the top bar opens both lists. Switch them off in Appearance > Customize > Top bar. To place them in a footer or header of your own, give a Group block the class "ariade-locale". Developers can add other plugins with the ariade_locale_languages and ariade_locale_currencies filters. * The recommended plugins notice now also lists TranslatePress and WPML Multilingual & Multicurrency for WooCommerce, for sites in more than one language or currency. = 1.7.128 = * New: a top bar above the header, the same as on the Ariade themes for Shopify and BigCommerce. It shows "Need help?" with Call, Email, Sign language and Contact links and an optional short message, and Ariade Pro puts its Listen and accessibility settings buttons at its start. On by default; set it up or switch it off in Appearance > Customize > Top bar. Each link shows only when filled in (Contact uses a published page called Contact until you choose one), and the bar is left out when it has nothing to show. On phones the links show as icons and stay readable to screen readers. Plugins can add their own buttons with the ariade_top_bar_start action and check ariade_top_bar_enabled(). = 1.7.127 = * Documentation links now open the new Ariade for WordPress documentation (https://ananyoo.com/ariade-accessible-wordpress-theme/documentation/): "Theme documentation & support" and "Get the demo plugin" on the Ariade dashboard (Appearance > Ariade), and the "Documentation" link in the branded footer, which pointed to /faq/. The readme lists the documentation next to the live demo. = 1.7.126 = * WooCommerce: the product video thumbnail's accessible name now includes its length exactly as it is shown on the thumbnail (for example "Show video: Ariade for WordPress in 90 seconds, 1:35"), so speech input users can say what they see (WCAG 2.5.3 Label in Name). It was read as "1 min 35 sec", which did not match the visible "1:35". = 1.7.125 = * WooCommerce: a product can show a YouTube video in its gallery. Set it in Products, edit a product, "Product video (Ariade)" box near the bottom of the right-hand column: a YouTube link, and optionally a title for screen readers, the length and a poster image. The video is the last thumbnail, with a play icon and its length. Choosing it shows the poster in the main frame with a play button; the player (youtube-nocookie.com, captions on) loads only when that button is pressed, and choosing a photo again stops it. Without a poster, YouTube's own thumbnail is used. = 1.7.124 = * WooCommerce: the "Add to cart" button now sits right next to the quantity box. Every WooCommerce button had a 1.1rem margin on both sides, which also indented the review Submit button and the Log in, Register and Reset password buttons from the fields above them. Buttons now have no side margins; buttons side by side keep a small gap, and a notice keeps its text off its button. * WooCommerce: the stock line on a product page ("25 in stock") is now an outlined pill with an icon (a tick in stock, a cross out of stock, a clock on backorder), so it no longer reads as part of the description. The icon and words carry the state, not colour alone, and it stays visible in Windows high contrast mode. = 1.7.123 = * WooCommerce: on a product page, the stars and the "customer review" link now sit on one centred line, lined up with the left edge of the title and just under it. WooCommerce's empty clearing element sat first in the row and pushed the stars right, its 0.5em top margin pushed them below the link, and the title kept the full block gap above the row. = 1.7.122 = * WooCommerce: on a phone, headings in a product description were smaller than the text under them, because WordPress fluid type takes h3 down to about 15px while the text is 17px. Headings in the Description panel now stay larger than the text at every screen width. = 1.7.121 = * WooCommerce: headings in a product description had no space above or below them. theme.css sets h1 to h4 to margin:0 because block layouts add their own gaps, but a product description is plain HTML without those gaps. Headings and lists in the Description panel now have normal spacing. * WooCommerce: an open Description or Additional information panel was capped at 1600px, so a long description was cut off, on a phone often by a third or more. An open panel now has no height limit, and the open and close slide is kept. * WooCommerce: a closed panel is now hidden from the keyboard and screen readers as well as from view. Before, links inside a closed panel could still take focus while out of sight (WCAG 2.4.7). The slide is turned off for visitors who ask for reduced motion. = 1.7.120 = * WooCommerce: in the cart, the crossed-out regular price of an item on sale was a light grey with a contrast of 3.1:1. It is now darker (5.9:1), so it meets WCAG 1.4.3. = 1.7.119 = * WooCommerce: on a product page, the "Additional information" panel now appears only when the product really has attributes, weight or dimensions. A test that was always true used to show an empty panel on every product, downloads included. Its subtitle now names the fields it holds instead of a fixed "Colour, size, dimension & weight". * WooCommerce: the "Product details" band is left out on a product that has no description and nothing else to list, instead of showing a heading with nothing under it. * WooCommerce: the category buttons above the shop list only categories that have products a visitor can see, so a button never opens an empty page. * WooCommerce: the band at the top of the cart page has a button back to the shop: "Continue shopping" when the cart has items, "Browse the shop" while it is empty. * WooCommerce: the band at the top of the cart page now follows the cart. It was printed when the page loaded, so after adding an item from "New in store" it still said "Your cart is empty" above a full cart; it now updates its title and subtotal whenever the cart changes. * WooCommerce: a crossed-out sale price on a product page (including the price shown after choosing a variation) and in related products is no longer faded by WooCommerce's own 50% opacity, so it keeps enough contrast (WCAG 1.4.3). * WooCommerce: the quantity box and "Add to cart" button on a product page now line up with the text above them. An empty clearing element from WooCommerce sat first in the row and pushed them in, and on a product sold one at a time the hidden quantity box added a second gap. = 1.7.118 = * Blog: in the Aurora single post header, a long post title now uses the full header width with evenly balanced lines instead of a narrow 22-character column, so long titles no longer wrap into four or five lines. The excerpt under it can run to 80 characters per line. Short titles, and all titles on phones, look the same as before. = 1.7.117 = * Performance: the preloaded heading font is now Barlow Semi Condensed SemiBold (600), the weight most headings use, instead of Bold. Headings no longer shift when the font arrives, which lowers layout shift (CLS) on pages with a large intro heading. = 1.7.116 = * WooCommerce: while a product is being added to the cart, its "Add to cart" button stays solid navy with white text instead of fading to grey, so the text keeps enough contrast (WCAG 1.4.3). = 1.7.115 = * WooCommerce cart: the items card now has side padding. Product images no longer touch the left edge, prices and the "Total" heading no longer touch the right edge, on desktop and on phones. On phones the line total no longer gets cut off at the right edge of the card. = 1.7.114 = * WooCommerce: on small screens the store notice icon now sits at the top, next to the first line of a message that wraps, instead of in the middle. = 1.7.113 = * WooCommerce: on the My account page the store notice now lines up with the account content (same width and side padding). * WooCommerce: no focus ring is drawn around a store notice when WooCommerce moves focus to it for screen readers. The notice is not a control; the "View cart" button inside it keeps its own focus ring. = 1.7.112 = * WooCommerce: the store notice styles from 1.7.111 now win over the WooCommerce block stylesheets that load after the theme, so the padding and rounded right corners show as designed. The notice also lines up with the left and right edges of the cart and checkout content instead of sitting indented. = 1.7.111 = * WooCommerce: store notices such as "added to your cart" now show under the page title instead of above it. The page, full title, checkout and a new cart template place the WooCommerce Store Notices block right after the page title area. Before this, the cart page used the plugin's own template, which printed the notice above the title. * WooCommerce: block store notices are styled to match the theme. The icon, the message and the button sit on one vertical centre line, the bar is flat on the left with rounded right corners, and the "View cart" button is a pill with a visible focus ring. On small screens the button wraps under the message. * WooCommerce: the "View cart" button is hidden inside notices on the cart page itself, because the visitor is already there. * Classic WooCommerce notices use the same flat left bar with rounded right corners. = 1.7.110 = * Fonts go back to font-display: fallback (the WordPress default) instead of swap from 1.7.106. With swap, headings first drew in a system font and then jumped when the narrower Barlow font arrived, which counted as layout shift (CLS) in Lighthouse. With fallback the browser waits a moment for the preloaded font, so text appears once, in the right font. The smaller font files from 1.7.109 make that wait shorter. = 1.7.109 = * Performance: each theme font is now split into two files, the way Google Fonts does it. The first holds the Latin letters, numbers, punctuation, arrows and common currency signs (including the euro and rupee) that almost every page uses; the second holds Latin Extended, Vietnamese, Greek and Cyrillic and downloads only on a page that contains those characters. A typical page downloads about 35% less font data. Letters look exactly the same. The original full font files are still included for child themes that point to them. = 1.7.108 = * Performance: the site logo (your own or the bundled Ariade logo) no longer takes the page's one "high priority" image slot, so it goes to the hero, featured or product image that visitors see first. * Performance: on a single product page, the main product image loads with high priority and is never lazy loaded. = 1.7.107 = * Performance: on pages and single posts, the post's own featured image at the top now loads with high priority (fetchpriority="high"), so it shows sooner. Post cards in blog lists are not changed. = 1.7.106 = * Performance: the theme fonts use font-display: swap, so text shows at once in a system font and changes to the theme font when it arrives. * Performance: the carousel excerpt rule moved into theme.css, so a page with an Ananyoo carousel no longer loads the whole portfolio stylesheet for that one rule. It looks the same. * Removed three site-specific rules (one site's home page trust badges) that did not belong in the theme; they also made such a page load the whole blog stylesheet. = 1.7.105 = * Single post: when the breadcrumb is on, the category pill above the title shows the category as plain text if the breadcrumb already links to it, so the two are not the same link side by side. It looks the same. = 1.7.104 = * Pricing patterns: the price and its "per project" line are one paragraph, so the price is no longer reported as a possible heading. It looks the same. * About (chapters) pattern: each big number and its caption are one paragraph, for the same reason. It looks the same. * About (spine) pattern: the pink team role text is a deeper pink, so it meets 4.5:1 contrast on white. * Services listing: the card arrow is no longer a paragraph, so it is not reported as a possible heading. * Single post (aurora): only the author link is underlined, not the text around it. * Shop: the "Select options" and out-of-stock rule from 1.7.103 now also covers WooCommerce block product grids, such as the suggestions on an empty cart. = 1.7.103 = * Accessibility: every decorative icon the theme prints (shop, category, account, product tabs, gallery zoom, home and starter patterns) now has aria-hidden on the SVG itself, so no checker reports it as an image without a text alternative. * Accessibility: the footer logo image has an empty alt, because its link already says "Ariade - back to top". It no longer repeats the header logo's text. * Shop: each grid button's accessible name now starts with its visible text ("Add to cart: Focus Notebook", "Select options: Contrast Coffee Mug"), so speech input matches what is on screen (WCAG 2.5.3). * Shop: "Select options" opens the product page at its options; an out-of-stock product shows "Out of stock" instead of a second "Read more" link to the same page. * Pagination: Previous and Next links (blog, archives, shop and plugin lists) go straight to the main content of the new page, and are no longer the same link as the page number beside them. * Page hero: the subtitle under the page title is no longer reported as a possible heading. It looks the same. * Product page: the price is printed in a