Guide on 瓶子裡的小狐狸

Pokemon Pokopia 夢島全面攻略：每日限定資源島指南

Wed, 25 Mar 2026 15:08:09 +0100

解鎖條件

當玩家與飄飄球（Drifloon）成為夥伴後，即可解鎖每日限定的夢島（Dream Island）功能。

島嶼特性

夢島為每日可造訪一次的特殊地點，內含大量稀有物資與礦石，如金礦與寶可金屬。島上不會出現野生寶可夢，但能拾取素材、物品製作方法與收藏品。

⚠️ 提醒：島嶼會在每日結束時自動重置。所有未帶回的道具將會遺失，因此務必在每日結束前離島並清空資源。

探險目標

主要任務是徹底蒐集所有資源，並在當日結束前安全返回基地。

建議玩家攜帶足夠的背包空間，以免遺漏高價值礦物。

Pokemon Pokopia 喜歡的東西

Fri, 20 Mar 2026 17:17:07 +0100

Pokémon Pokopia 中喜好完全一致的寶可夢群組大部分都是同一進化鏈，也有比較特別的是跨族相同的情況：水箭龜＆黏美龍、拉普拉斯＆水君這類組合。以下列出喜好相同的寶可夢供大家參考。在Y CHEUNG 做的 Pokémon Pokopia 寶可夢圖鑒網站中也可以在寶可夢詳情popup中直接看到擁有相同喜好的寶可夢是誰。

Pokémon Pokopia 食物味道分類匯總

Thu, 19 Mar 2026 16:28:15 +0100

Pokémon Pokopia 中可送給寶可夢吃的食物自己（百變怪）吃料理可以強化技能，餵寶可夢滿足喜好可以提升舒適度，供奉萌苔卡比獸獲得Buff加成。

1. 苦苦的

查看喜歡苦苦的寶可夢有哪些

Pokémon Pokopia 料理食譜指南

Wed, 18 Mar 2026 21:07:20 +0100

Pokémon Pokopia 中共有24道料理，分為沙拉、湯、麵包、漢堡排四類，每類6種，依星級（⭐️、⭐️⭐️、⭐️⭐️⭐️）和6種味道（原味、甜、苦、辣、澀、酸）區分。

Tiny Adventure Oddities Guide: All Five Qinghe Locations for Where Winds Meet v1.3

Sat, 07 Feb 2026 19:35:05 +0100

The game Where winds Meet has updated to v1.3, , launching the new Spring Festival event. Under Joyful Activities, you’ll find a section called Tiny Adventure.

1. Tiny Adventure

A sprawling world for a minature figure. Five daily chapters and new coolectibles/Oddities await. The gamplay and quest remain available after the event ends.

This post focuses on the Oddities. In the Qinghe map, you can collect 5 special Oddities. Gathering all of them rewards you with 19 random Inner Ways.

產品成功秘笈：AARRR 框架的產品指標大全

Wed, 26 Jun 2024 02:11:38 +0800

1. 什麼是AARRR框架？

AARRR 框架，又稱為「海盜模型」，它是由 Dave McClure 於2007年提出的數據分析框架，用於追蹤和優化用戶的五個關鍵階段：獲取、激活、保留、收入和推薦。

薩爾達傳說王國之淚攻略 - 餘料建造武器合成

Sat, 08 Jul 2023 08:11:12 +0000

薩爾達傳說王國之淚中的餘料建造技能可以合成武器，使用一把武器，再加上一個材料，就能使武器或攻擊力加成，或增加屬性攻擊，因此最佳解就是使用原本就帶有特殊效果性能的武器與屬性材料合成。

薩爾達傳說王國之淚攻略 - 料理食譜/藥劑配方大全

Fri, 09 Jun 2023 13:46:46 +0000

這一作薩爾達傳說的料理清單可以在料理選項卡中按下 X 鍵，打開料理備忘錄查看。

Zelda game capture

💡本文在PC上可以用 Ctrl + F , Mac上用 Command+ F 檢索。

WCAG 2.1 Guidelines

Thu, 03 Nov 2022 07:51:12 +0000

Guideline	WCAG 2.1 Success Criteria Name and Conformance Level	WCAG 2.1 Success Criteria Description	WCAG Version	How to Meet the Criteria
1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.	1.1.1 Non-text Content (A)	All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. • Controls, Input: If non-text content is a control or accepts user input, then it has a Name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) • Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) • Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content. • Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content. • CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. • Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.	WCAG 2.0	1.1.1 Non-text Content Techniques and Failures
1.2 Time-based Media: Provide alternatives for time-based media.	1.2.1 Audio-only and Video-only (Pre-recorded) (A)	For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such: • Pre-recorded Audio-only: An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content. • Pre-recorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for pre-recorded video-only content.	WCAG 2.0	1.2.1 Audio-only and Video-only (Pre-recorded) Techniques and Failures
	1.2.2 Captions (Pre-recorded) (A)	Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labelled as such.	WCAG 2.0	1.2.2 Captions (Pre-recorded) Techniques and Failures
	1.2.3 Audio Description or Media Alternative (Pre-recorded) (A)	An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labelled as such.	WCAG 2.0	1.2.3 Audio Description or Media Alternative (Pre-recorded) Techniques and Failures
	1.2.4 Captions (Live) (AA)	Captions are provided for all live audio content in synchronized media .	WCAG 2.0	1.2.4 Captions (Live) Techniques and Failures
	1.2.5 Audio Description (Prerecorded) (AA)	Audio description is provided for all prerecorded video content in synchronized media.	WCAG 2.0	1.2.5 Audio Description (Prerecorded) Techniques and Failures
1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.	1.3.1 Info and Relationships (A)	Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.	WCAG 2.0	1.3.1 Info and Relationships Techniques and Failures
	1.3.2 Meaningful Sequence (A)	When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.	WCAG 2.0	1.3.2 Meaningful Sequence Techniques and Failures
	1.3.3 Sensory Characteristics (A)	Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. Note: For requirements related to color, refer to Guideline 1.4.	WCAG 2.0	1.3.3 Sensory Characteristics Techniques and Failures
	1.3.4 Orientation (AA)	Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where binary display orientation is not applicable	WCAG 2.1	1.3.4 Orientation Techniques and Failures
	1.3.5 Identify Input Purpose (AA)	The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for form input data.	WCAG 2.1	1.3.5 Identify Input Purpose Techniques and Failures
1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.	1.4.1 Use of Color (A)	Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.	WCAG 2.0	1.4.1 Use of Color Techniques and Failures
	1.4.2 Audio Control (A)	If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-interference.	WCAG 2.0	1.4.2 Audio Control Techniques and Failures
	1.4.3 Contrast (Minimum) (AA)	The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; • Incidental: Text or images of text that are part of an inactive user interface component , that are pure decoration , that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.	WCAG 2.0	1.4.3 Contrast (Minimum) Techniques and Failures
	1.4.4 Resize Text (AA)	Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.	WCAG 2.0	1.4.4 Resize Text Techniques and Failures
	1.4.5 Images of Text (AA)	If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: • Customizable: The image of text can be visually customized to the user's requirements; • Essential: A particular presentation of text is essential to the information being conveyed. Note: Logotypes (text that is part of a logo or brand name) are considered essential.	WCAG 2.0	1.4.5 Images of Text Techniques and Failures
	1.4.10 Reflow (AA)	Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: •Vertical scrolling content at a width equivalent to 320 CSS pixels; •Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. Note: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom. Note: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content.	WCAG 2.1	1.4.10 Reflow Techniques and Failures
	1.4.11 Non-text Contrast (AA)	The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): •User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; •Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.	WCAG 2.1	1.4.11 Non-text Contrast Techniques and Failures
	1.4.12 Text Spacing (AA)	In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: •Line height (line spacing) to at least 1.5 times the font size; •Spacing following paragraphs to at least 2 times the font size; •Letter spacing (tracking) to at least 0.12 times the font size; •Word spacing to at least 0.16 times the font size. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.	WCAG 2.1	1.4.12 Text Spacing Techniques and Failures
	1.4.13 Content on Hover or Focus (AA)	Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: •Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; •Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; •Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. Note: Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute. Note: Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.	WCAG 2.1	1.4.13 Content on Hover or Focus Techniques and Failures
2.1 Keyboard Accessible: Make all functionality available from a keyboard.	2.1.1 Keyboard (A)	All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.	WCAG 2.0	2.1.1 Keyboard Techniques and Failures
	2.1.2 No Keyboard Trap (A)	: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.	WCAG 2.0	2.1.2 No Keyboard Trap Techniques and Failures
	2.1.4 Character Key Shortcuts (A)	If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: •Turn off: A mechanism is available to turn the shortcut off; •Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc.); •Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.	WCAG 2.1	2.1.4 Character Key Shortcuts Techniques and Failures
2.2 Enough Time: Provide users enough time to read and use content.	2.2.1 Timing Adjustable (A)	For each time limit that is set by the content, at least one of the following is true: • Turn off: The user is allowed to turn off the time limit before encountering it; or • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the spacebar"), and the user is allowed to extend the time limit at least ten times; or • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or • Essential Exception: The time limit is essential and extending it would invalidate the activity; or • 20 Hour Exception: The time limit is longer than 20 hours. Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.	WCAG 2.0	2.2.1 Timing Adjustable Techniques and Failures
	2.2.2 Pause, Stop, Hide (A)	For moving, blinking, scrolling, or auto-updating information, all of the following are true: • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential ; and • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3. Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.	WCAG 2.0	2.2.2 Pause, Stop, Hide Techniques and Failures
2.3 Seizures: Do not design content in a way that is known to cause seizures.	2.3.1 Three Flashes or Below Threshold (A)	Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.	WCAG 2.0	2.3.1 Three Flashes or Below Threshold Techniques and Failures
2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.	2.4.1 Bypass Blocks (A)	A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.	WCAG 2.0	2.4.1 Bypass Blocks Techniques and Failures
	2.4.2 Page Titled (A)	Web pages have titles that describe topic or purpose.	WCAG 2.0	2.4.2 Page Titled Techniques and Failures
	2.4.3 Focus Order (A)	If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.	WCAG 2.0	2.4.3 Focus Order Techniques and Failures
	2.4.4 Link Purpose (In Context) (A)	The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.	WCAG 2.0	2.4.4 Link Purpose (In Context) Techniques and Failures
	2.4.5 Multiple Ways (AA)	More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process .	WCAG 2.0	2.4.5 Multiple Ways Techniques and Failures
	2.4.6 Headings and Labels (AA)	Headings and labels describe topic or purpose.	WCAG 2.0	2.4.6 Headings and Labels Techniques and Failures
	2.4.7 Focus Visible (AA)	Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.	WCAG 2.0	2.4.7 Focus Visible Techniques and Failures
2.5 Input Modalities: Make it easier for users to operate functionality through various inputs beyond keyboard.	2.5.1 Pointer Gestures (A)	All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. Note: This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).	WCAG 2.1	2.5.1 Pointer Gestures Techniques and Failures
	2.5.2 Pointer Cancellation (A)	For functionality that can be operated using a single pointer, at least one of the following is true: •No Down-Event: The down-event of the pointer is not used to execute any part of the function; •Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; •Up Reversal: The up-event reverses any outcome of the preceding down-event; •Essential: Completing the function on the down-event is essential. Note: Functions that emulate a keyboard or numeric keypad key press are considered essential. Note: This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).	WCAG 2.1	2.5.2 Pointer Cancellation Techniques and Failures
	2.5.3 Label in Name (A)	For user interface components with labels that include text or images of text, the name contains the text that is presented visually. Note: A best practice is to have the text of the label at the start of the name.	WCAG 2.1	2.5.3 Label in Name Techniques and Failures
	2.5.4 Motion Actuation (A)	Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: •Supported Interface: The motion is used to operate functionality through an accessibility supported interface; •Essential: The motion is essential for the function and doing so would invalidate the activity.	WCAG 2.1	2.5.4 Motion Actuation
3.1 Readable: Make text content readable and understandable.	3.1.1 Language of Page (A)	The default human language of each web page can be programmatically determined.	WCAG 2.0	3.1.1 Language of Page Techniques and Failures
	3.1.2 Language of Parts (AA)	The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.	WCAG 2.0	3.1.2 Language of Parts Techniques and Failures
3.2 Predictable: Make Web pages appear and operate in predictable ways.	3.2.1 On Focus (A)	When any component receives focus, it does not initiate a change of context.	WCAG 2.0	3.2.1 On Focus Techniques and Failures
	3.2.2 On Input (A)	Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.	WCAG 2.0	3.2.2 On Input Techniques and Failures
	3.2.3 Consistent Navigation (AA)	Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.	WCAG 2.0	3.2.3 Consistent Navigation Techniques and Failures
	3.2.4 Consistent Identification (AA)	Components that have the same functionality within a set of Web pages are identified consistently.	WCAG 2.0	3.2.4 Consistent Identification Techniques and Failures
3.3 Input Assistance: Help users avoid and correct mistakes.	3.3.1 Error Identification (A)	If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.	WCAG 2.0	3.3.1 Error Identification Techniques and Failures
	3.3.2 Labels or Instructions (A)	Labels or instructions are provided when content requires user input.	WCAG 2.0	3.3.2 Labels or Instructions Techniques and Failures
	3.3.3 Error Suggestion (AA)	If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.	WCAG 2.0	3.3.3 Error Suggestion Techniques and Failures
	3.3.4 Error Prevention (Legal, Financial, Data) (AA)	For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: 1. Reversible: Submissions are reversible. 2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. 3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.	WCAG 2.0	3.3.4 Error Prevention (Legal, Financial, Data) Techniques and Failures
4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.	4.1.1 Parsing (A)	In content implemented using mark-up languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.	WCAG 2.0	4.1.1 Parsing Techniques and Failures
	4.1.2 Name, Role, Value (A)	For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.	WCAG 2.0	4.1.2 Name, Role, Value Techniques and Failures
	4.1.3 Status Messages (AA)	In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.	WCAG 2.1	4.1.3 Status Messages Techniques and Failures

《星之卡比探索發現》世界地圖全關卡任務一覽

Wed, 06 Apr 2022 11:25:37 +0000

這些天因為Covid-19 疫情嚴重封城，Y Cheung在家把新到手的《星之卡比探索發現》一週目給通關了！可喜可賀🎉！

通關後查看遊戲進度是66%，嗯，非常吉利！

《星之卡比探索發現》禮物關鍵詞快遞密碼列表

Sat, 02 Apr 2022 05:43:20 +0000

在《星之卡比探索發現》遊戲關卡中解救50個瓦豆魯迪（Waddle Dee）後，探索據點瓦豆魯迪小鎮中解鎖瓦豆魯迪快遞建築，開始使用禮物關鍵詞獲取大禮包！

Go to the Waddle Dee-liveries, confirm to use password, and input your password.

這裡是輸入禮物關鍵詞就能獲得禮物的瓦豆魯迪快遞！

只要連接網路，還能夠使用網路上已公開的禮物關鍵詞喔。

要在瓦豆魯迪快遞使用禮物關鍵詞嗎？

為了確認快遞禮物，正在執行網路連接……

那麼，就麻煩你輸入禮物關鍵詞了。

SEO 結構化資料指南

Fri, 23 Apr 2021 11:09:00 +0000

結構化資料是一種標準化格式，它提供網頁相關資訊並將網頁內容分類，有助於優化搜索引擎SEO。

⚠ 即使網頁已正確加上標記，Google 也不能保證結構化資料一定會出現在搜尋結果中。

GDPR 簡介

Sun, 15 Nov 2020 07:10:57 +0000

General Data Protection Regulation (EU GDPR)《一般資料保護規範》是在歐盟法律中對所有歐盟個人關於資料保護和隱私的規範，涉及了歐洲境外的個人資料出口。GDPR 主要目標為取回個人對於個人資料的控制，以及為了國際商務而簡化在歐盟內的統一規範。（wiki）

動物森友會之釣魚大會攻略

Sat, 11 Jul 2020 10:59:54 +0000

釣魚大會規則

在限制時間3分鐘內盡可能釣到最多的魚。

釣魚大會參加人員

同時在島上的所有好友都能參加。

釣魚大會舉辦時間

早上 9 時至下午 6 時

釣魚大會參加方法

在廣場與與俞司廷對話報名參加，報名費一次500鈴錢，第一次免費。

釣魚大會點數獲得規則

釣到的魚每條1點，釣到3條以上則額外獲得2點。例如釣到5條魚，可獲得 5 * 1 + 2 = 7 點。

與好友一起參加會有額外點數，5～9條可獲得額外5點，10～14條可獲得額外7點，15條以上可獲得額外10點。例如你個人釣到5條魚，好友們總共釣到15條魚，你個人可獲得 5 * 1 + 2 + 10 = 17 點。

圖形庫（Graphics API）簡介

Mon, 01 Jun 2020 04:15:25 +0000

OpenGL (https://www.opengl.org/) Open Graphics Library 是跨語言跨平台的底層圖形庫，用於渲染2D、3D矢量圖形，由Khronos Group維護。

OpenGL ES (https://www.khronos.org/opengles/) OpenGL for Embedded Systems 是OpenGL的子集，專為手機等嵌入式設備而設計。

《集合啦！動物森友會》新手指南

Tue, 14 Apr 2020 07:19:35 +0000

物品可以隨便放在地上。
釣到的魚，抓到的昆蟲，以及挖到的化石每種各留1只留著不賣，等著捐給博物館。
初期優先以增加哩數為目標，在還完5000哩的移民債后，先兌換口袋整理技巧（5000哩），令道具欄擴充。
用哩數兌換道具收藏環后，按◀▶鍵切換道具，按▲鍵打開道具收藏環，按▼鍵收回道具。
在自己島上不要吃水果。不要吃水果后打石頭，會打爆石頭。石頭再生非常慢。
解鎖過河的撐竿跳竿子，需要博物館長傅達搬來島上后取得。
解鎖爬山的梯子，需要完成建造商店后取得。
初期最快賺錢方法是去外島釣魚，或者晚上抓狼蛛。
在釣魚前撒魚飼料，提高釣到新品種的幾率。魚飼料的DIY方程式在第一次用鏟子在沙灘上挖到蛤蜊時取得。
在外島看到未擁有的樹木時，可吃水果后用鏟子整株挖下帶回。
每日與島上的居民交談可至少獲得3個DIY方程式。
按住B鍵可以加快對話速度。
整理道具欄時，按住A鍵可以抓住物品移動位置。
鮮花可以穿戴在身上。
砸石頭的時候，站在石頭旁，在你的左右和後方各挖一個洞，再開始擊打石頭。快速連續擊打石頭，最多可獲得7樣物品。
每日搖樹可獲得2家具5黃蜂及若干金幣。
搖樹或撞樹時遇到黃蜂，可以用捕蟲網捕捉它。如果不幸被叮，去店裏買藥或者自己製作藥（蜂巢+草）或者與某居民對話獲得藥，吃藥治療。如果不及時治療，被叮第二次的時候你會暈倒並傳送囘自己屋子。
公告欄上有黃色的鳥停在上面時，表示有新的公告要閲讀。
空中飄過的氣球用彈弓射下，可獲得禮物或金錢。
地上發光的地方用鏟子挖開可獲得10000金幣，埋入金錢種植金錢樹，可得3倍的金錢。

挖金幣

射氣球

《集合啦！動物森友會》博物館指南

Tue, 14 Apr 2020 06:02:58 +0000

動物森友會是任天堂情報開發本部開發並由任天堂發行的社交模擬系列，遊戲中玩家生活在一個由擬人動物居住的村莊，展開各種活動。系列以其開放性著稱，並大量使用遊戲機內置時鐘和日曆模擬真實時間。

本地開發測試郵件服務 Mailhog

Wed, 25 Mar 2020 05:00:31 +0000

Mailhog真乃本地開發測試郵件服務的神器，方便好用。

Mailhog 項目

Y cheung 使用docker來啟動mailhog服務，docker-composer.yml文件內容如下

寶可夢幫幫忙任務攻略

Fri, 27 Dec 2019 05:54:37 +0000

寶可幫幫忙（日文︰ポケジョブ，英文︰Poké Job）是伽勒爾地區上通過對寶可夢委託工作而使其成長的機制。它有兩種類型，一種是提升經驗值的任務，一種是提升個體值的任務。

Pokemon 劍盾招式類別

Sun, 22 Dec 2019 05:33:57 +0000

Pokemon 劍盾中4號道路告示板上說：

寶可夢的招式可分為2種。分別是物理招式與特殊招式！寶可夢的攻擊越高，物理招式就會越強！寶可夢的特攻越高，特殊招式就會越強！

八方旅人角色一览

Thu, 05 Sep 2019 15:16:04 +0000

简单做了一个八方旅人各主角的基本情况表格，方便组队选择队员。 excel表格贴过来全乱了，只好提供图片了。

類別	細項	剑士*奥伯里克	舞者*普蕾米罗斯	商人*泰瑞莎	药师*阿尔芬	猎人*翰伊特	盗贼*提利昂	学者*塞拉斯	神官*欧菲莉亚
武器	剑	V					V
	枪	V		V
	短剑		V				V
	斧				V	V
	弓			V		V
	杖							V	V
攻击属性	冰				V			V
	火						V	V
	雷							V
	风			V
	光								V
	暗		V
场景指令	获得信息				V			V
	获得援助		V						V
	获得物品			V			V
	对战	V				V
人物属性(最大LV）	HP	5781	4002	4891	5336	4447	4447	3557	4002
	SP	145	182	182	182	145	145	218	236
	物攻	342	285	313	313	342	256	256	285
	物防	313	199	285	285	228	313	256	285
	属攻	256	342	313	285	285	285	370	342
	属防	228	228	285	285	228	228	342	370
	命中	313	285	285	228	342	313	285	285
	速度	285	370	256	228	285	342	256	228
	暴击	285	285	256	285	313	285	228	199
	回避	285	313	256	285	313	342	285	228

初次試用Hotjar服务

Wed, 10 Dec 2014 07:24:02 +0000

HOTJAR是個新的網站服務，用來分析用戶瀏覽網頁行為的，它提供Heatmaps, Session Playback, Proactive Chat, Polls, Funnel Analysis, Polls and Surveys等。

目前還是beta版，點這裡申請免費使用帳戶6個月，也算是早鳥票XD

facebook anniversary video

Sun, 23 Nov 2014 08:28:46 +0000

刚才Facebook上线突然看到官方通知，要我制作感谢视频给朋友。真是……又不是感恩节，这是做哪门子的感谢视频啊摔！

制作感谢视频URL

只有短短30秒的视频呢….